Website review, no card needed
citygate.co.uk website review
Visit site (opens in a new tab)Reviewed 27 October 202645 issues · 94 checks
This review found 45 issues worth fixing on citygate.co.uk, 15 of them high impact, across 94 checks. The most urgent: reduce unused JavaScript. 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
74CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 2.4 s |
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.2 s |
| Jun 6, 2026 | 2.2 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.2 s |
| Jul 4, 2026 | 2.2 s |
| Jul 11, 2026 | 2.2 s |
| Jul 18, 2026 | 2.2 s |
| Jul 25, 2026 | 2.3 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.3 s |
| Aug 15, 2026 | 2.3 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.3 s |
| Sep 5, 2026 | 2.3 s |
| Sep 12, 2026 | 2.3 s |
| Sep 19, 2026 | 2.3 s |
| Sep 26, 2026 | 2.3 s |
| Oct 3, 2026 | 2.3 s |
| Oct 10, 2026 | 2.3 s |
| Oct 17, 2026 | 2.3 s |
| Oct 24, 2026 | 2.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 155 ms |
| May 16, 2026 | 154 ms |
| May 23, 2026 | 156 ms |
| May 30, 2026 | 158 ms |
| Jun 6, 2026 | 161 ms |
| Jun 13, 2026 | 162 ms |
| Jun 20, 2026 | 165 ms |
| Jun 27, 2026 | 170 ms |
| Jul 4, 2026 | 173 ms |
| Jul 11, 2026 | 177 ms |
| Jul 18, 2026 | 178 ms |
| Jul 25, 2026 | 179 ms |
| Aug 1, 2026 | 179 ms |
| Aug 8, 2026 | 184 ms |
| Aug 15, 2026 | 191 ms |
| Aug 22, 2026 | 192 ms |
| Aug 29, 2026 | 195 ms |
| Sep 5, 2026 | 195 ms |
| Sep 12, 2026 | 188 ms |
| Sep 19, 2026 | 191 ms |
| Sep 26, 2026 | 192 ms |
| Oct 3, 2026 | 194 ms |
| Oct 10, 2026 | 200 ms |
| Oct 17, 2026 | 203 ms |
| Oct 24, 2026 | 197 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
Reduce unused JavaScript
4.7 s · 875 KiBAbout 875 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.7 s faster on a phone.
Use efficient cache lifetimes
2.9 s · 799 KiB20 files are served with short cache lifetimes, so returning visitors download them again (799 KiB).
Improve image delivery
1.9 s · 539 KiB4 images could be 539 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.
Mobile performance score: 38
38/100Your mobile performance score is 38 (desktop: 66). 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 (Google Tag Manager, Facebook and Stripe and others), adding 1.6 MB and 1.1 s of main-thread time.
Google Tag Manager adds 422 ms
422 msGoogle Tag Manager costs a phone 422 ms of main-thread work and 390 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.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 361 ms. During a long task the page ignores taps.
Main-thread work: 3.0 s
A phone's processor spends 3.0 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Facebook adds 253 ms
253 msFacebook costs a phone 253 ms of main-thread work and 311 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.
Render-blocking requests
200 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 200 ms.
Legacy JavaScript
58 KiBPolyfills for old browsers add 58 KiB JavaScript that modern phones do not need.
Reduce unused CSS
29 KiBAbout 29 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 66 but mobile only 38. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify CSS
8 KiB8 KiB could be saved by minifying CSS.
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: 64 ms
64 msYour server sent the HTML in 64 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.
Largest Contentful Paint: 25.4 s
25.4 sYour largest element takes 25.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Discover automotive excellence: New & Used vehicles from th…”.
Time to Interactive: 25.4 s
25.4 sThe page becomes fully interactive after 25.4 s. Good is under 3.8 s.
First Contentful Paint: 5.3 s
5.3 sThe first text or image appears after 5.3 s on a phone. Good is under 1.8 s.
Speed Index: 9.8 s
9.8 sVisually, the page fills in at 9.8 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 803 ms
803 msScripts block taps and scrolling for 803 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 220 ms
220 msReal visitors wait 220 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 29% slower for real visitors
+29%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 155 ms to 197 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 424 ms
424 msReal visitors wait 424 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.034
0.034The layout barely moves while loading (CLS 0.034, good is under 0.1).
Images and page weight
Page weight: 3.9 MB in 126 requests
3.9 MBYour homepage downloads 3.9 MB in 126 requests on a phone: scripts 2.7 MB (50), images 944 KiB (10) and other files 189 KiB (59). Under 2 MB keeps phones on slow connections fast.
3 images far larger than shown
405 KiB3 images are downloaded at several times the size a phone draws them, for example 71db748864bf17e649b75bd859ac1944:61147e9ecea18258c4def24f310 at 600 px wide, shown at 90 px. Resized copies would save about 405 KiB.
4 images below the first screen load straight away
4 images further down the page (550 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 1.1 g of CO₂ per visit
1.11 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.11 g of CO₂e: 133.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Unlabelled dropdowns
2 dropdowns have no label.
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
2 elements hidden from screen readers can still receive keyboard focus.
Positive tabindex
2 elements have a tabindex above 0, which scrambles the keyboard order.
All page content should be contained by landmarks (28 elements)
All page content should be contained by landmarks: 28 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
14 links without text
14 visible links have no text or label, so screen readers cannot say where they go.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (4 elements)
Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3, h3 → h6 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 4 images in the HTML carry an alt attribute.
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 11 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (15 characters)
Your title is only 15 characters: “Home | Citygate”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“Citygate” and “Citygate”). One clear main headline is easier for people and search engines.
No XML sitemap
No XML sitemap at https://citygate.co.uk/sitemap-index.xml, so Google discovers your pages only by following links.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
125 internal links, 16 external
The homepage links to 125 pages on citygate.co.uk and 16 external pages.
4 checks passed
Meta description: 110 characters
Your meta description is 110 characters: “The UK's leading Volkswagen, ŠKODA, SEAT, CUPRA & Kia dealer with 37 Locations across London & the South East.”.
Canonical URL set
The canonical URL is https://citygate.co.uk/.
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 and points crawlers to your sitemap.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://citygate.co.uk/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (707 words), so crawlers that don't run JavaScript still read it.
Other pages
2 linked pages hidden from search
https://citygate.co.uk/fleet-and-business and https://citygate.co.uk/vwfs-rent-a-car are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
15 pages share a meta description
https://citygate.co.uk/locations, https://citygate.co.uk/customer-feedback, https://citygate.co.uk/vw-commercial, https://citygate.co.uk/fleet-and-business, https://citygate.co.uk/vwfs-rent-a-car and https://citygate.co.uk/careers and 9 others use the same meta description. A description written for each page earns more clicks.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 78 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
2 checks passed
Tap targets are thumb-sized
33 of 38 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
Thin social proof
Social proof on the homepage: 5 testimonial or review blocks. 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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 705 words of copy
The homepage carries about 705 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book Service or MOT”.
4 calls to action
The homepage has 4 calls to action, for example “Contact us”, “Book Service or MOT” and “Sign up!”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and Hotjar.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
17 cookies set on arrival
17Opening the homepage sets 17 cookies (measured from a US location before any click).
30 other companies contacted
Loading the homepage contacts 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) loads with the page.
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 citygate.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
- Framework
- Gatsby
- Analytics
- Google Tag Manager | Hotjar
- Hosting
- Netlify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 45 issues on citygate.co.uk, including 17 speed issues, 6 SEO issues and 4 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.