Website review, no card needed
abbeyroad.com website review
Visit site (opens in a new tab)Reviewed 20 October 202644 issues · 85 checks
This review found 44 issues worth fixing on abbeyroad.com, 18 of them high impact, across 85 checks. The most urgent: improve image delivery. 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
70CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.4 s |
| May 9, 2026 | 2.4 s |
| May 16, 2026 | 2.5 s |
| May 23, 2026 | 2.5 s |
| May 30, 2026 | 2.6 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.5 s |
| Jun 20, 2026 | 2.5 s |
| Jun 27, 2026 | 2.5 s |
| Jul 4, 2026 | 2.6 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.6 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.5 s |
| Aug 22, 2026 | 2.5 s |
| Aug 29, 2026 | 2.5 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.8 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 114 ms |
| May 9, 2026 | 114 ms |
| May 16, 2026 | 116 ms |
| May 23, 2026 | 117 ms |
| May 30, 2026 | 116 ms |
| Jun 6, 2026 | 113 ms |
| Jun 13, 2026 | 113 ms |
| Jun 20, 2026 | 114 ms |
| Jun 27, 2026 | 116 ms |
| Jul 4, 2026 | 118 ms |
| Jul 11, 2026 | 118 ms |
| Jul 18, 2026 | 118 ms |
| Jul 25, 2026 | 119 ms |
| Aug 1, 2026 | 121 ms |
| Aug 8, 2026 | 123 ms |
| Aug 15, 2026 | 126 ms |
| Aug 22, 2026 | 126 ms |
| Aug 29, 2026 | 123 ms |
| Sep 5, 2026 | 122 ms |
| Sep 12, 2026 | 121 ms |
| Sep 19, 2026 | 123 ms |
| Sep 26, 2026 | 128 ms |
| Oct 3, 2026 | 129 ms |
| Oct 10, 2026 | 132 ms |
| Oct 17, 2026 | 135 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
How it loaded on a phone
1.1 s
2.3 s
3.4 s
4.5 s
5.7 s
6.8 s
7.9 s
9.0 s
Speed
Improve image delivery
17.0 s · 5.9 MB7 images could be 5.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 17.0 s faster on a phone.
Use efficient cache lifetimes
1.1 s · 5.1 MB43 files are served with short cache lifetimes, so returning visitors download them again (5.1 MB).
Render-blocking requests
1.4 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Font display
1.0 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.0 s).
Mobile performance score: 45
45/100Your mobile performance score is 45 (desktop: 30). 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 transcend-cdn.com and others), adding 4.3 MB and 921 ms of main-thread time.
Reduce unused JavaScript
470 ms · 387 KiBAbout 387 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 470 ms faster on a phone.
Reduce unused CSS
470 ms · 82 KiBAbout 82 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 470 ms faster on a phone.
Google Tag Manager adds 484 ms
484 msGoogle Tag Manager costs a phone 484 ms of main-thread work and 505 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.
cloudfront.net adds 0 ms
0 mscloudfront.net costs a phone 0 ms of main-thread work and 3.4 MB 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 234 ms. During a long task the page ignores taps.
Minify CSS
160 ms · 21 KiB21 KiB could be saved by minifying CSS.
Minify JavaScript
15 KiB15 KiB could be saved by minifying JavaScript.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 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.
2 checks passed
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 998 ms of it running JavaScript. That is comfortably low.
Server response: 4 ms
4 msYour server sent the HTML in 4 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: 20.8 s
20.8 sYour largest element takes 20.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Abbey Road is the home of music making. We’re the world’s f…”.
Time to Interactive: 25.6 s
25.6 sThe page becomes fully interactive after 25.6 s. Good is under 3.8 s.
Speed Index: 12.6 s
12.6 sVisually, the page fills in at 12.6 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Largest content (LCP) got 21% slower for real visitors
+21%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.4 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.5 s
2.5 sReal visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.6 s
1.6 sReal visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 419 ms
419 msScripts block taps and scrolling for 419 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.182
0.182The layout shifts by 0.182 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 17% slower for real visitors
+17%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 114 ms to 135 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 147 ms
147 msReal visitors wait 147 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.02
0.02For real visitors the layout shifts by 0.02 (75th percentile). Good is under 0.1.
Images and page weight
Page weight: 9.1 MB in 77 requests
9.1 MBYour homepage downloads 9.1 MB in 77 requests on a phone: images 7.3 MB (15), scripts 1.1 MB (25) and fonts 565 KiB (5). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
ChristmasQuartetBanner1.png weighs 3.4 MB. On a phone connection a single image that size takes seconds.
1 image far larger than shown
2.9 MB1 image is downloaded at several times the size a phone draws it, for example ChristmasQuartetBanner1.png at 2,720 px wide, shown at 366 px. Resized copies would save about 2.9 MB.
1 image in older formats
1 image (3.4 MB) is JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
About 2.6 g of CO₂ per visit
2.58 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.58 g of CO₂e: 309.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
33 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 37 WCAG 2.2 A/AA and best-practice rules on the phone render: 33 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No robots.txt
There is no robots.txt at abbeyroad.com/robots.txt, the first file search crawlers ask for.
91 internal links, 19 external
The homepage links to 91 pages on abbeyroad.com and 19 external pages.
3 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “Grammy award-winning engineers, incredible gear, and the best spaces, innovation, learning and events, to create and ca…”.
Title: 36 characters
Your title is a healthy 36 characters: “Abbey Road: The Home of Music Making”.
XML sitemap found
Your XML sitemap is reachable at https://www.abbeyroad.com/sitemap.xml.
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://www.abbeyroad.com/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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (723 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages without a meta description
https://www.abbeyroad.com/the-studios, https://www.abbeyroad.com/gear-instruments, https://www.abbeyroad.com/filming, https://www.abbeyroad.com/stem-mastering and https://www.abbeyroad.com/dolby-atmos-mastering have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages without an H1
https://www.abbeyroad.com/the-studios, https://www.abbeyroad.com/the-penthouse, https://www.abbeyroad.com/thefrontroom, https://www.abbeyroad.com/themixstage, https://www.abbeyroad.com/gear-instruments and https://www.abbeyroad.com/technical-services and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
4 pages slow to respond
https://www.abbeyroad.com/studio-three, https://www.abbeyroad.com/themixstage, https://www.abbeyroad.com/gear-instruments and https://www.abbeyroad.com/filming took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 44 found) and read each the way a search engine does.
5 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
4 broken images
4 images failed to load on a phone, for example https://ids4.ad.gt/api/v1/ip_match?id=AU1D-0100-001792512528-Z2P937EA-QQZK.
2 JavaScript errors while loading
2 errors were 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
7 of 7 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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 543 words of copy
The homepage carries about 543 words of visible text.
4 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Shop” and “Sign up now”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 2 mores (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
13 cookies set on arrival
13Opening the homepage sets 13 cookies, 2 of them by other companies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
38 other companies contacted
Loading the homepage contacts 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 abbeyroad.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Bootstrap
- Analytics
- Google Tag Manager
Company
- Founded
- 1931
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on abbeyroad.com, including 22 speed issues, 5 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.