Website review, no card needed
aftv.co.uk website review
Visit site (opens in a new tab)Reviewed 19 October 202641 issues · 76 checks
This review found 41 issues worth fixing on aftv.co.uk, 11 of them high impact, across 76 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Apr 25, 2026 | 4.5 s |
| May 2, 2026 | 4.4 s |
| May 9, 2026 | 4.6 s |
| May 16, 2026 | 4.6 s |
| May 23, 2026 | 4.7 s |
| May 30, 2026 | 4.8 s |
| Jun 6, 2026 | 4.8 s |
| Jun 13, 2026 | 4.9 s |
| Jun 20, 2026 | 4.8 s |
| Jun 27, 2026 | 4.9 s |
| Jul 4, 2026 | 5.0 s |
| Jul 11, 2026 | 5.0 s |
| Jul 18, 2026 | 5.1 s |
| Jul 25, 2026 | 5.0 s |
| Aug 1, 2026 | 4.9 s |
| Aug 8, 2026 | 5.0 s |
| Aug 15, 2026 | 5.0 s |
| Aug 22, 2026 | 5.1 s |
| Aug 29, 2026 | 5.3 s |
| Sep 5, 2026 | 5.0 s |
| Sep 12, 2026 | 4.6 s |
| Sep 19, 2026 | 4.1 s |
| Sep 26, 2026 | 3.7 s |
| Oct 3, 2026 | 3.4 s |
| Oct 10, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Apr 25, 2026 | 138 ms |
| May 2, 2026 | 136 ms |
| May 9, 2026 | 142 ms |
| May 16, 2026 | 130 ms |
| May 23, 2026 | 132 ms |
| May 30, 2026 | 130 ms |
| Jun 6, 2026 | 127 ms |
| Jun 13, 2026 | 128 ms |
| Jun 20, 2026 | 125 ms |
| Jun 27, 2026 | 133 ms |
| Jul 4, 2026 | 136 ms |
| Jul 11, 2026 | 136 ms |
| Jul 18, 2026 | 146 ms |
| Jul 25, 2026 | 143 ms |
| Aug 1, 2026 | 130 ms |
| Aug 8, 2026 | 139 ms |
| Aug 15, 2026 | 139 ms |
| Aug 22, 2026 | 149 ms |
| Aug 29, 2026 | 187 ms |
| Sep 5, 2026 | 192 ms |
| Sep 12, 2026 | 195 ms |
| Sep 19, 2026 | 184 ms |
| Sep 26, 2026 | 173 ms |
| Oct 3, 2026 | 170 ms |
| Oct 10, 2026 | 161 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Render-blocking requests
2.3 s21 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Reduce unused JavaScript
1.3 s · 630 KiBAbout 630 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.
Main-thread work: 14.2 s
A phone's processor spends 14.2 s on main-thread work while loading, 6.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Rubicon Project adds 1.2 s
1.2 sRubicon Project costs a phone 1.2 s of main-thread work and 160 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 37
37/100Your mobile performance score is 37 (desktop: 67). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Rubicon Project, Pubmatic and Snack Media and others), adding 1.3 MB and 3.4 s of main-thread time.
Pubmatic adds 672 ms
672 msPubmatic costs a phone 672 ms of main-thread work and 99 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Use efficient cache lifetimes
50 ms · 451 KiB173 files are served with short cache lifetimes, so returning visitors download them again (451 KiB).
Snack Media adds 459 ms
459 msSnack Media costs a phone 459 ms of main-thread work and 212 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 455 ms. During a long task the page ignores taps.
Ad Lightning adds 382 ms
382 msAd Lightning costs a phone 382 ms of main-thread work and 85 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Reduce unused CSS
300 ms · 41 KiBAbout 41 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Taboola adds 178 ms
178 msTaboola costs a phone 178 ms of main-thread work and 377 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Minify CSS
130 ms · 9 KiB9 KiB could be saved by minifying CSS.
Minify JavaScript
36 KiB36 KiB could be saved by minifying JavaScript.
Legacy JavaScript
27 KiBPolyfills for old browsers add 27 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 67 but mobile only 37. A gap that wide usually means heavy scripts and images that hit phones hardest.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Time to Interactive: 43.1 s
43.1 sThe page becomes fully interactive after 43.1 s. Good is under 3.8 s.
Largest Contentful Paint: 8.4 s
8.4 sYour largest element takes 8.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Total Blocking Time: 2.2 s
2.2 sScripts block taps and scrolling for 2.2 s in total while the page loads. Good is under 200 ms.
Speed Index: 7.0 s
7.0 sVisually, the page fills in at 7.0 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 138 ms to 161 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Real-user INP: 170 ms
170 msReal visitors wait 170 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Largest content (LCP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 4.5 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.004
0.004The layout barely moves while loading (CLS 0.004, good is under 0.1).
Images and page weight
Page weight: 3.2 MB in 1,226 requests
3.2 MBYour homepage downloads 3.2 MB in 1,226 requests on a phone: scripts 1.7 MB (80), other files 502 KiB (487) and images 426 KiB (447). Under 2 MB keeps phones on slow connections fast.
About 0.9 g of CO₂ per visit
0.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 107.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 link without text
1 link has no text or label, so screen readers cannot say where it goes.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
Every image has alt text
All 8 images in the HTML carry an alt attribute.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “AFTV - The Biggest Arsenal Fan Network | News, Videos & Fan Opinion”.
Meta description is long (175 characters)
Your meta description is 175 characters; Google truncates after about 160, so the end of your pitch is cut.
One H1 headline
Your <h1> is empty.
57 internal links, 26 external
The homepage links to 57 pages on aftv.co.uk and 26 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://aftv.co.uk/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, Place and WebPage.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://aftv.co.uk/sitemap.xml.
AI search readiness
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and description; contact details would complete it.
llms.txt published
The site publishes https://aftv.co.uk/llms.txt (2 KiB, 22 links), a plain-text guide to the site for AI tools.
Other pages
4 linked pages are broken
Your homepage links to https://aftv.co.uk/category/womens, https://aftv.co.uk/category/academy, https://aftv.co.uk/category/transfers and https://aftv.co.uk/match-centre/nottingham-forest-0-1-arsenal-five-things-we-learned-as-noni-madueke-delivers-again-for-mikel-arteta, which answer with an error. Visitors hit a dead end and search engines drop them.
2 pages share a title
https://aftv.co.uk/match-centre and https://aftv.co.uk/category/match-centre all use the title “Arsenal FC Fixtures, Results & Where To Watch Matches - AFTV”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages without a meta description
https://aftv.co.uk/contact, https://aftv.co.uk/write-for-us, https://aftv.co.uk/recommended-sites, https://aftv.co.uk/podcasts, https://aftv.co.uk/author/subhojyotibasu and https://aftv.co.uk/author/harry-dalton have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://aftv.co.uk/match-centre and https://aftv.co.uk/category/match-centre use the same meta description. A description written for each page earns more clicks.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://aftv.co.uk/category/match-centre, whose canonical is https://aftv.co.uk/match-centre. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
6 pages without an H1
https://aftv.co.uk/about-aftv, https://aftv.co.uk/contact, https://aftv.co.uk/write-for-us, https://aftv.co.uk/news, https://aftv.co.uk/match-centre and https://aftv.co.uk/category/match-centre have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://aftv.co.uk/podcasts has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 27 found) and read each the way a search engine does.
2 checks passed
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 11 pages that loaded have a <title>.
Best practices
27 third-party cookies
27 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 2 deprecated browser APIs that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
21 console errors
21 errors were logged to the browser console during Google's test (“Failed to load resource: net::ERR_CONNECTION_FAILED”).
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 3 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 358 words of copy
The homepage carries about 358 words of visible text.
3 checks passed
5 calls to action
The homepage has 5 calls to action, for example “Contact”, “Shop” and “DOWNLOAD AFTV+ APP”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at aftv.co.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on aftv.co.uk, including 23 speed issues, 3 SEO issues and 2 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.