Website review, no card needed

chessington.com logo

chessington.com website review

Visit site (opens in a new tab)Reviewed 30 October 202633 issues · 82 checks

This review found 33 issues worth fixing on chessington.com, 10 of them high impact, across 82 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of chessington.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. chessington.com at 0.4 s0.4 s
  2. chessington.com at 0.8 s0.8 s
  3. chessington.com at 1.3 s1.3 s
  4. chessington.com at 1.7 s1.7 s
  5. chessington.com at 2.1 s2.1 s
  6. chessington.com at 2.5 s2.5 s
  7. chessington.com at 2.9 s2.9 s
  8. chessington.com at 3.4 s3.4 s

Speed

11 to fix48
  • Use efficient cache lifetimes

    1.9 s · 5.6 MB

    35 files are served with short cache lifetimes, so returning visitors download them again (5.6 MB).

  • Mobile performance score: 48

    48/100

    Your mobile performance score is 48. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Main-thread work: 4.7 s

    A phone's processor spends 4.7 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Google Tag Manager, Facebook and Optanon and others), adding 1.2 MB and 1.3 s of main-thread time.

  • Render-blocking requests

    950 ms

    3 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.

  • Google Tag Manager adds 621 ms

    621 ms

    Google Tag Manager costs a phone 621 ms of main-thread work and 395 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.

  • Facebook adds 374 ms

    374 ms

    Facebook costs a phone 374 ms of main-thread work and 297 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 · 92 KiB

    About 92 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.

  • 20 long tasks on the main thread

    20 long tasks block the main thread while loading, the longest for 334 ms. During a long task the page ignores taps.

  • Reduce unused JavaScript

    325 KiB

    About 325 KiB of JavaScript is downloaded but never used on this page.

  • 2,079 HTML elements

    The page has 2,079 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Improve image delivery

    200 ms · 90 KiB

    6 images could be 90 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.

  • Legacy JavaScript

    97 KiB

    Polyfills for old browsers add 97 KiB JavaScript that modern phones do not need.

  • 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

1 checks passed
  • Server response: 14 ms

    14 ms

    Your server sent the HTML in 14 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix100
  • Time to Interactive: 15.3 s

    15.3 s

    The page becomes fully interactive after 15.3 s. Good is under 3.8 s.

  • Total Blocking Time: 1.4 s

    1.4 s

    Scripts block taps and scrolling for 1.4 s in total while the page loads. Good is under 200 ms.

  • Largest Contentful Paint: 5.3 s

    5.3 s

    Your largest element takes 5.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “From £62 per person Christmas Short Breaks Book Now”.

  • Speed Index: 6.0 s

    6.0 s

    Visually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.

  • First Contentful Paint: 2.0 s

    2.0 s

    The first text or image appears after 2.0 s on a phone. Good is under 1.8 s.

7 checks passed
  • Passes Core Web Vitals for real visitors

    Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).

  • Real-user LCP: 1.1 s

    1.1 s

    Real visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 166 ms

    166 ms

    Real visitors wait 166 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 0.8 s

    0.8 s

    Real visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 320 ms

    320 ms

    Real visitors wait 320 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Cumulative Layout Shift: 0.004

    0.004

    The layout barely moves while loading (CLS 0.004, good is under 0.1).

Images and page weight

1 to fix70
  • Page weight: 8.2 MB in 75 requests

    8.2 MB

    Your homepage downloads 8.2 MB in 75 requests on a phone: media 4.8 MB (3), images 1.8 MB (19) and scripts 1.1 MB (27). Under 2 MB keeps phones on slow connections fast.

  • About 2.3 g of CO₂ per visit

    2.33 g

    By the Sustainable Web Design model, a visit to your homepage emits about 2.33 g of CO₂e: 279.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

3 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

3 to fixGoogle 8895
  • 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.

  • 3 text elements with low contrast

    3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

  • 6 links without text

    6 visible links have no text or label, so screen readers cannot say where they go.

  • Headings skip levels

    Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 26 images in the HTML carry an alt attribute.

  • 49 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 9285
  • Meta description is long (173 characters)

    Your meta description is 173 characters; Google truncates after about 160, so the end of your pitch is cut.

  • Structured data has 1 problem

    Structured data found (ImageGallery, ImageObject, VideoObject and WebSite) but with 1 problem, for example “WebSite: missing name”.

  • No robots.txt

    There is no robots.txt at chessington.com/robots.txt, the first file search crawlers ask for.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

  • 255 internal links, 18 external

    The homepage links to 255 pages on chessington.com and 18 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Christmas Short Breaks”.

  • Title: 59 characters

    Your title is a healthy 59 characters: “Chessington World of Adventures Resort: UK Theme Park & Zoo”.

  • Canonical URL set

    The canonical URL is https://www.chessington.com/.

  • Open Graph tags complete

    Open Graph tags are complete, so shared links show a title, description and image.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.chessington.com/sitemap.xml.

AI search readiness

1 to fix81
  • 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.

1 checks passed
  • Text is in the HTML

    Your server sends the page's text in the HTML (1,414 words), so crawlers that don't run JavaScript still read it.

Other pages

3 to fix83
  • 1 linked page hidden from search

    https://www.chessington.com/umbraco is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 1 page without a meta description

    https://www.chessington.com/umbraco has no meta description, so Google writes the search snippet from whatever text it finds.

  • 1 page without an H1

    https://www.chessington.com/umbraco has no <h1> headline, so visitors and search engines get no clear main topic.

  • 5 pages slow to respond

    https://www.chessington.com/plan-your-visit/before-you-visit/accessibility-guide, https://www.chessington.com/schools, https://www.chessington.com/our-company/blog, https://www.chessington.com/umbraco and https://www.chessington.com/tickets-passes took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 93 found) and read each the way a search engine does.

4 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 7791
  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

2 checks passed
  • Tap targets are thumb-sized

    63 of 71 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix83
  • 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.

  • 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 map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • 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 934 words of copy

    The homepage carries about 934 words of visible text.

  • Urgency cues

    The page uses urgency cues (a countdown or limited-time wording).

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Book Now” and “Buy Now”.

  • 29 calls to action

    The homepage has 29 calls to action, for example “Contact Us”, “Online Shop” and “Download the App”.

  • 3 short forms

    3 short forms (1 field at most) are right on the homepage.

  • Social proof on the page

    Social proof on the homepage: 6 testimonial or review blocks, 1 customer or partner logo and a star rating.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Opening hours shown

    Your opening hours are on the homepage.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Tag Manager 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.

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 cookies (measured from a US location before any click).

  • 14 other companies contacted

    Loading the homepage contacts 14 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 chessington.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

  • The footer still says © 2024.

Stack

Analytics
Google Tag Manager
Hosting
Azure

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 33 issues on chessington.com, including 16 speed issues, 4 SEO issues and 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25