Error message

  • Deprecated function: Return type of Aws\HandlerList::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 32 of /var/www/html/vendor/aws/aws-sdk-php/src/HandlerList.php).
  • Deprecated function: Return type of Aws\Api\AbstractModel::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Api/AbstractModel.php).
  • Deprecated function: Return type of Aws\Api\AbstractModel::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Api/AbstractModel.php).
  • Deprecated function: Return type of Aws\Api\AbstractModel::offsetSet($offset, $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 include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Api/AbstractModel.php).
  • Deprecated function: Return type of Aws\Api\AbstractModel::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Api/AbstractModel.php).
  • Deprecated function: Return type of Aws\Endpoint\Partition::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 13 of /var/www/html/vendor/aws/aws-sdk-php/src/Endpoint/Partition.php).
  • Deprecated function: Return type of & Aws\Endpoint\Partition::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 13 of /var/www/html/vendor/aws/aws-sdk-php/src/Endpoint/Partition.php).
  • Deprecated function: Return type of Aws\Endpoint\Partition::offsetSet($offset, $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 include() (line 13 of /var/www/html/vendor/aws/aws-sdk-php/src/Endpoint/Partition.php).
  • Deprecated function: Return type of Aws\Endpoint\Partition::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 13 of /var/www/html/vendor/aws/aws-sdk-php/src/Endpoint/Partition.php).
  • Deprecated function: Aws\Credentials\Credentials implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in include() (line 8 of /var/www/html/vendor/aws/aws-sdk-php/src/Credentials/Credentials.php).
  • Deprecated function: Return type of Aws\Command::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Command.php).
  • Deprecated function: Return type of & Aws\Command::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Command.php).
  • Deprecated function: Return type of Aws\Command::offsetSet($offset, $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 include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Command.php).
  • Deprecated function: Return type of Aws\Command::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Command.php).
  • Deprecated function: Return type of Aws\Command::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Command.php).
  • Deprecated function: Return type of Aws\Command::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Command.php).
  • Deprecated function: Return type of Aws\Result::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 9 of /var/www/html/vendor/aws/aws-sdk-php/src/Result.php).
  • Deprecated function: Return type of & Aws\Result::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 9 of /var/www/html/vendor/aws/aws-sdk-php/src/Result.php).
  • Deprecated function: Return type of Aws\Result::offsetSet($offset, $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 include() (line 9 of /var/www/html/vendor/aws/aws-sdk-php/src/Result.php).
  • Deprecated function: Return type of Aws\Result::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 9 of /var/www/html/vendor/aws/aws-sdk-php/src/Result.php).
  • Deprecated function: Return type of Aws\Result::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 9 of /var/www/html/vendor/aws/aws-sdk-php/src/Result.php).
  • Deprecated function: Return type of Aws\Result::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 9 of /var/www/html/vendor/aws/aws-sdk-php/src/Result.php).
  • Warning: Undefined array key "nid" in views_handler_field_term_node_tid->pre_render() (line 98 of /var/www/html/docroot/sites/all/modules/views/modules/taxonomy/views_handler_field_term_node_tid.inc).
  • Warning: Undefined array key "nid" in views_handler_field_term_node_tid->pre_render() (line 98 of /var/www/html/docroot/sites/all/modules/views/modules/taxonomy/views_handler_field_term_node_tid.inc).
×

Entertainment

We Rank Each EPL Club Twitter Handle And No. 1 Might Surprise You, But No. 20 Won't

By Travis Yoesting September 11, 2017
Featured Image
Manchester United has the most followers, but @ManUtd isn’t No. 1 on our list.
Twitter

Twitter handles are like facts: Everyone has their own and some are better than others. The English Premier League follows this model. Some EPL Twitter handles are instantly recognizable, like @ManUtd with its 14 million followers and @Arsenal with another 11.3 million. Some, like @htafcdotcom, leave you scratching your head as to whether you’re following an English Premier League club or a realty website. 

Twitter handles matter. When clubs are tagged in tweets, followers see the handle and not the full name. When @NBCSportsSoccer tweets a video of @LFC scoring a goal, do you immediately think of Liverpool? What about Leicester City, Leeds United, Lyon or León? 

We have therefore sought out to rank the English Premier League club Twitter handles based on brevity, clarity and the ability to be recognized immediately. Note: These highly scientific rankings are based purely on the handles and names of the feeds, not the contents of the tweets themselves. 

1
Everton

Everton @Everton 

Followers: 1.31M

Everton does everything right. It’s simple, clean, concise and you immediately know when you see @Everton it’s referring to that other team in Liverpool. 

2
Arsenal

Arsenal FC @Arsenal

Followers: 11.3M

Arsenal almost follows Everton’s example in doing everything right but for one caveat: the FC in the Twitter name. Aided by a recognizable name and its bright, vibrant red color, Arsenal’s Twitter feed is second only to Manchester United in followers, despite not really being relevant in the EPL title race in a decade. 

3
Bournemouth

AFC Bournemouth @afcbournemouth 

Followers: 319K

Bournemouth earns a spot in the top three for one reason and one reason alone: the cherry emoji. Only one other EPL club has an emoji in its name and really, it’s the cherry (sorry not sorry) on top of an otherwise solid handle/name combination. 

4
Chelsea

Chelsea FC @ChelseaFC 

Followers: 9.91M

Chelsea, Southampton and Watford are all in the same boat coming in ranked 4-6, but Chelsea gets the nod at No. 4 for a better header photo. Chelsea would have been better served with a simple @Chelsea, but that handle was apparently already taken by some “internet girl” living in New York. She’s got 28.3K followers, so she’s no scrub. 

5
Watford

Watford FC @WatfordFC 

Followers: 374K

Unfortunately for Watford, @watford was taken by an unofficial account with 784 followers. But @WatfordFC is completely satisfactory. Bonus points for the club’s great patch logo.

 

6
Southampton

Southampton FC @SouthamptonFC 

Followers: 850K

Southampton is the last of the three because its photo is uninspiring and grainy and the profile photo doesn’t even give a straight look at the club logo. You can do better than that, Saints. It doesn’t help that @Southampton is taken by an account that’s been inactive for more than a year and has a whopping 393 followers. 

7
Stoke City

Stoke City FC @stokecity 

Followers: 829K

Stoke City would have been ranked ahead of the three above had it not been for one overlooked factor: not capitalizing the S and C. By not capitalizing the letters, Stoke unnecessarily convolutes the handle, but full points for brevity. 

8
Manchester City

Manchester City @ManCity

Followers: 4.83M

In a close race between Manchester City and Manchester United, City edges its more decorated rival because it doesn’t have to abbreviate anything other than Manchester. 

9
Manchester United

Manchester United @ManUtd 

Followers: 14M

The most followed club in the league, Manchester United has an instantly recognizable handle, but much of that is down to the ubiquity of the club itself. Having to abbreviate both Manchester and United docks the Red Devils to nearly outside the Top 10 despite its 14 million followers, though to be fair Manchester is way too long of a city name for a handle. 

10
West Ham

West Ham United @WestHamUtd 

Followers: 1.27M

Barely making it into the Top 10 are the Hammers, who may have been better served shortening the handle to just @WestHam, a handle that was available as recently as 2016. Again points off for abbreviating United, though probably a good choice given the length of the handle. 

 

11
West Brom

West Bromwich Albion @WBA 

Followers: 722K

West Brom had a lot of options with its handle given its name and we’ll give @WBA the first spot in the bottom half of the table on brevity alone. While @WestBrom would have been more immediately recognizable, the club redeems itself by making its Twitter name West Bromwich Albion. It is a bit too close to @WNBA, unfortunately. 

12
Liverpool

Liverpool FC @LFC 

Followers: 8.45M

As mentioned at the top, when you see @LFC, there are a lot of clubs that could come to mind. While none of those clubs have won as many EPL titles as Liverpool, the ambiguity docks the Reds all the way down to No. 12. At least @liverpool is a decent and active handle with 563K followers. 

13
Leicester City

Leicester City @LCFC 

Followers: 1.05M

Five years ago, an @LCFC handle would have left most confused as to what club was being represented. The Foxes have gained loads of popularity in the last few years, but as with Liverpool the handle is too vague to rank any higher.

14
Newcastle United

Newcastle United FC @NUFC 

Followers: 1.14M

Unfortunately for Newcastle United, the first thing many people think of when they hear the word “Newcastle” is the wonderful brown ale. @Newcastle has a fraction of the followers (50K) of the football club, but the Magpies are stuck with a handle that, while brief, has little instant recognition. 

15
Crystal Palace

Crystal Palace F.C. @CPFC 

Followers: 602K

There’s nothing inherently wrong with @CPFC. It’s shorter, but given that @CrystalPalace was available as recently as 2013, the Eagles probably should have gone with a handle that’s more readily comes across as being for the football club.

 

16
Burnley

Burnley FC @BurnleyOfficial

Followers: 281K

Nos. 16-18 all fall under the same category in having to tag “Official” in the handle. Nothing says late to the party like throwing an “Official” or “Real” on a Twitter handle. Burnley didn’t join until 2011. Way to get with the program, guys.

17
Swansea City

Swansea City AFC @SwansOfficial 

Followers: 811K

Swansea ranks behind Burnley because it doesn’t even have the full Swansea name. The Swans, who bafflingly didn’t join Twitter until 2012, could have had plenty of options, from @SwansAFC, @SwanseaAFC and even @Swansea had it acted a little quicker. 

18
Tottenham

Tottenham Hotspur @SpursOfficial 

Followers: 2.28M

Given the amount of variations available to Tottenham, settling on a handle with “Official” in it is a bit disappointing and, frankly, unacceptable. It doesn’t help that there’s another sports team (with way more titles and history of success) taking the @Spurs handle, with half a million more followers too. 

19
Brighton & Hove Albion

BHAFC @OfficialBHAFC 

Followers: 149K

There’s a lot wrong here so let’s get started. First, not only does the handle have “Official” in it, but it comes before the actual club name. No bueno. Then, the club has a long, convoluted acronym. Being new to the Premier League, Brighton & Hove Albion has the disadvantage of not being well-known, so to have a handle that doesn’t have come close to the actual name does not help. And the fact the name of the club isn't even in the Twitter name, it's hard to figure out what exactly you're looking at, though the soccer ball emoji is a small saving grace. To be fair, the name of the club itself is a bit silly. Are you Brighton or are you Hove? Pick a side!

20
Huddersfield Town

Huddersfield Town @htafcdotcom 

Followers: 119K

Let’s be honest, when we talk about bad Twitter handles, Huddersfield Town is who we’re thinking about. Besides the fact Huddersfield Town is a newly promoted team few know much about, the club muddles it by creating a handle so far from the actual name you have to think for a long minute (or five) before realizing who the handle is for. Even if you get a chance to see the name, you still probably won’t think it’s a soccer club. It’s no surprise it’s the lowest-followed feed of all the EPL clubs. 

The18 Recommends For You

Videos you might like