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":6176122738,"date":"2012-11-21T19:02:34","date_gmt":"2012-11-21T19:02:34","guid":{"rendered":"http:\/\/digital-football.com\/?p=6176122738"},"modified":"2012-11-21T19:05:16","modified_gmt":"2012-11-21T19:05:16","slug":"chelsea-fc-defeat-and-sacking-generates-2-5m-twitter-mentions","status":"publish","type":"post","link":"http:\/\/digital-football.com\/featured\/chelsea-fc-defeat-and-sacking-generates-2-5m-twitter-mentions\/","title":{"rendered":"Chelsea FC defeat and sacking generates 2.5m Twitter mentions"},"content":{"rendered":"Football Social Media yet again showed how influential it was today with the news that Chelsea FC<\/a> had recorded an astonishing 2.5 million mentions in less than 24 hours. The current European champions have had a traumatic 24 hours – starting with last nights 3-0 defeat to Juventus, their highest Champions League loss ever. Then, this morning the Blues announced that their manager Roberto Di Matteo had become the 8th manager in 9 years to be sacked by the club – with the tweet being retweeted over 5,000 times.<\/p>\n<\/p>\n
Twitter covered the busy day on their\u00a0UK blog<\/a>, highlighting the following as key stats:<\/p>\n\n- \u2023\u00a0The mentions spiked at about 9am today in the UK when Chelsea broke the news of their managers sacking via Twitter<\/li>\n
- \u2023\u00a0‘Chelsea’ as a keyword was tweeted over 1 million times<\/li>\n
- \u2023\u00a0Chelsea dominated the Twitter trends – with up to 5 individual items trending about the story in the UK, followed by it trending worldwide<\/li>\n
- \u2023\u00a0The story also trended worldwide<\/li>\n<\/ul>\n
This is a prime example of how powerful Social Media channels have become in football. The fact that Chelsea chose to break the news about Di Matteo’s sacking via Twitter shows how much times have changed, whereas previously print, radio and television would’ve been first to the bite.<\/p>\n