Deprecated: Creation of dynamic property autoptimizeImages::$lazyload_counter is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php on line 34

Deprecated: Creation of dynamic property autoptimizeCompatibility::$conf is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeCompatibility.php on line 18

Deprecated: Creation of dynamic property autoptimizeCriticalCSSCore::$criticalcss is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeCriticalCSSCore.php on line 20

Deprecated: Creation of dynamic property autoptimizeImages::$lazyload_counter is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php on line 34

Deprecated: Creation of dynamic property Smush\Core\Modules::$webp is deprecated in /home/swalsh/public_html/wp-content/plugins/wp-smushit/core/class-modules.php on line 109

Deprecated: Creation of dynamic property Jetpack_Publicize::$modules is deprecated in /home/swalsh/public_html/wp-content/plugins/jetpack/modules/publicize.php on line 38

Deprecated: Creation of dynamic property Automattic\Jetpack\Publicize\Publicize_UI::$in_jetpack is deprecated in /home/swalsh/public_html/wp-content/plugins/jetpack/modules/publicize.php on line 101

Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

Deprecated: http_build_query(): Passing null to parameter #2 ($numeric_prefix) of type string is deprecated in /home/swalsh/public_html/wp-includes/Requests/Transport/cURL.php on line 345

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php:34) in /home/swalsh/public_html/wp-includes/rest-api/class-wp-rest-server.php on line 1758
{"id":6176123478,"date":"2016-09-26T21:01:27","date_gmt":"2016-09-26T21:01:27","guid":{"rendered":"http:\/\/digital-football.com\/?p=6176123478"},"modified":"2016-09-27T11:48:20","modified_gmt":"2016-09-27T11:48:20","slug":"manchester-united-manutd-leads-twitter-growth-in-3-year-comparison","status":"publish","type":"post","link":"http:\/\/digital-football.com\/featured\/manchester-united-manutd-leads-twitter-growth-in-3-year-comparison\/","title":{"rendered":"Manchester United (@ManUtd) leads Twitter growth in 3 year comparison"},"content":{"rendered":"

\"manunitedaddidas\"<\/a><\/p>\n

Only three years ago the @ManUtd Twitter account languished behind the likes of Arsenal, Chelsea and Liverpool in terms of size and engagement, but how times have changed. Using data recorded by Digital-Football.com back in November 2013, we’ve compared where English Premier League clubs were then versus where they are now (plus a few new clubs in the league since then).<\/p>\n

It took only 70 days in 2013 for the @ManUtd account to hit 1 million followers<\/a>, but in less than 3 years the Mancunian giants have added an astonishing 7.3 million new followers (+505.98% growth).<\/p>\n\n\n<\/colgroup>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Club<\/strong><\/td>\nSep-16<\/strong><\/td>\nNov-13<\/strong><\/td>\nDifference<\/strong><\/td>\n%<\/strong><\/td>\n<\/tr>\n
manutd<\/td>\n8,800,000<\/td>\n1,452,195<\/td>\n7,347,805<\/td>\n505.98%<\/td>\n<\/tr>\n
arsenal<\/td>\n8,000,000<\/td>\n3,128,281<\/td>\n4,871,719<\/td>\n155.73%<\/td>\n<\/tr>\n
chelseafc<\/td>\n7,300,000<\/td>\n3,067,047<\/td>\n4,232,953<\/td>\n138.01%<\/td>\n<\/tr>\n
lfc<\/td>\n6,200,000<\/td>\n2,138,175<\/td>\n4,061,825<\/td>\n189.97%<\/td>\n<\/tr>\n
mancity<\/td>\n3,500,000<\/td>\n1,319,358<\/td>\n2,180,642<\/td>\n165.28%<\/td>\n<\/tr>\n
spursofficial<\/td>\n1,600,000<\/td>\n705,940<\/td>\n894,060<\/td>\n126.65%<\/td>\n<\/tr>\n
lcfc<\/td>\n836,100<\/td>\n<\/td>\n836,100<\/td>\n<\/td>\n<\/tr>\n
westhamutd<\/td>\n976,700<\/td>\n233,008<\/td>\n743,692<\/td>\n319.17%<\/td>\n<\/tr>\n
everton<\/td>\n939,900<\/td>\n275,635<\/td>\n664,265<\/td>\n240.99%<\/td>\n<\/tr>\n
southamptonfc<\/td>\n625,900<\/td>\n162,653<\/td>\n463,247<\/td>\n284.81%<\/td>\n<\/tr>\n
stokecity<\/td>\n593,700<\/td>\n151,756<\/td>\n441,944<\/td>\n291.22%<\/td>\n<\/tr>\n
swansofficial<\/td>\n610,100<\/td>\n176,690<\/td>\n433,410<\/td>\n245.29%<\/td>\n<\/tr>\n
sunderlandafc<\/td>\n582,300<\/td>\n180,514<\/td>\n401,786<\/td>\n222.58%<\/td>\n<\/tr>\n
wba<\/td>\n503,000<\/td>\n107,534<\/td>\n395,466<\/td>\n367.76%<\/td>\n<\/tr>\n
cpfc<\/td>\n422,700<\/td>\n70,609<\/td>\n352,091<\/td>\n498.65%<\/td>\n<\/tr>\n
watfordfc<\/td>\n235,900<\/td>\n<\/td>\n235,900<\/td>\n<\/td>\n<\/tr>\n
hullcity<\/td>\n282,200<\/td>\n61,624<\/td>\n220,576<\/td>\n357.94%<\/td>\n<\/tr>\n
afcbournemouth<\/td>\n207,400<\/td>\n<\/td>\n207,400<\/td>\n<\/td>\n<\/tr>\n
burnleyofficial<\/td>\n185,100<\/td>\n<\/td>\n185,100<\/td>\n<\/td>\n<\/tr>\n
boro<\/td>\n158,900<\/td>\n<\/td>\n158,900<\/td>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Even though fierce rivals Liverpool, Chelsea and Arsenal have added an incredible 4+ million in the same time period, only Crystal Palace come close in terms of relative growth seeing +498.65% November 13 to September 16.<\/p>\n

With transfer signings like Zlatan\u00a0Ibrahimovi\u0107 and Paul Pogba, it’s no surprise that United have stormed their way to the top of Twitter league tables. However, the real value of this huge growth isn’t just vanity metrics, but the sheer size of an alternate advertising platform that United now have. With an audience of over 8.8 million, the Red Devils have developed a social strategy that doesn’t just engage with looks to activate sponsor partnerships.<\/p>\n

With branded sponsored content from the likes of Chevrolet and adidas, United have been able to leverage their growth to presumably command better sponsorship deals and generate a new revenue stream. Quite simply, 3 years ago – this wasn’t happening on a major scale.<\/p>\n

 <\/p>\n

\n

When it comes to PKs and goal celebrations: practice makes perfect! #ChevroletMascots<\/a> pic.twitter.com\/fIpSjD0yPk<\/a><\/p>\n

\u2014 Chevrolet FC (@ChevroletFC) September 24, 2016<\/a><\/p><\/blockquote>\n