Website review, no card needed

shoprogerwaters.com logo

shoprogerwaters.com website review

Visit site (opens in a new tab)Reviewed 11 November 202632 issues · 72 checks

This review found 32 issues worth fixing on shoprogerwaters.com, 10 of them high impact, across 72 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

Real-visitor load time (LCP)75th percentile, phones
1.3 s973 msMay 23Nov 71.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.0 s
May 30, 20261.0 s
Jun 6, 20261.0 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 8, 20261.2 s
Sep 26, 20261.1 s
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.2 s
Nov 7, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
170 ms94 msMay 23Oct 31152 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026103 ms
May 30, 2026111 ms
Jun 6, 2026109 ms
Jun 27, 2026124 ms
Jul 4, 2026125 ms
Jul 11, 2026125 ms
Jul 18, 2026127 ms
Jul 25, 2026125 ms
Oct 3, 2026161 ms
Oct 10, 2026146 ms
Oct 17, 2026147 ms
Oct 24, 2026146 ms
Oct 31, 2026152 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

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

How it loaded on a phone

  1. shoprogerwaters.com at 0.4 s0.4 s
  2. shoprogerwaters.com at 0.8 s0.8 s
  3. shoprogerwaters.com at 1.1 s1.1 s
  4. shoprogerwaters.com at 1.5 s1.5 s
  5. shoprogerwaters.com at 1.9 s1.9 s
  6. shoprogerwaters.com at 2.3 s2.3 s
  7. shoprogerwaters.com at 2.7 s2.7 s
  8. shoprogerwaters.com at 3.0 s3.0 s

Speed

11 to fix44
  • Use efficient cache lifetimes

    2.0 s · 329 KiB

    12 files are served with short cache lifetimes, so returning visitors download them again (329 KiB).

  • Reduce unused JavaScript

    1.5 s · 364 KiB

    About 364 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Mobile performance score: 44

    44/100

    Your mobile performance score is 44. 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 Klaviyo and others), adding 1.6 MB and 966 ms of main-thread time.

  • Google Tag Manager adds 520 ms

    520 ms

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

    450 ms

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

  • Main-thread work: 3.9 s

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

  • 17 long tasks on the main thread

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

  • 2,276 HTML elements

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

  • Klaviyo adds 142 ms

    142 ms

    Klaviyo costs a phone 142 ms of main-thread work and 310 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.

  • Shopify adds 53 ms

    53 ms

    Shopify costs a phone 53 ms of main-thread work and 352 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.

  • Legacy JavaScript

    150 ms · 43 KiB

    Polyfills for old browsers add 43 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • Improve image delivery

    8 KiB

    1 image could be 8 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

1 checks passed
  • Server response: 8 ms

    8 ms

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

Core Web Vitals

6 to fix100
  • Largest Contentful Paint: 14.8 s

    14.8 s

    Your largest element takes 14.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Cart Roger Waters - This Is Not A Drill - Live From Prague …”.

  • Time to Interactive: 15.7 s

    15.7 s

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

  • Speed Index: 8.1 s

    8.1 s

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

  • Total Blocking Time: 968 ms

    968 ms

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

  • Tap response (INP) got 39% slower for real visitors

    +39%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 103 ms to 152 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • First Contentful Paint: 1.9 s

    1.9 s

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

  • Largest content (LCP) got 16% slower for real visitors

    +16%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

6 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.2 s

    1.2 s

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

  • Real-user INP: 152 ms

    152 ms

    Real visitors wait 152 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.

  • Cumulative Layout Shift: 0.001

    0.001

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

Images and page weight

1 to fix85
  • Page weight: 2.8 MB in 226 requests

    2.8 MB

    Your homepage downloads 2.8 MB in 226 requests on a phone: scripts 1.5 MB (89), other files 737 KiB (91) and images 364 KiB (11). Under 2 MB keeps phones on slow connections fast.

  • About 0.8 g of CO₂ per visit

    0.81 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.81 g of CO₂e: 96.9 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

Google 100100
2 checks passed
  • Every image has alt text

    All 9 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

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

SEO

4 to fixGoogle 9275
  • No meta description

    No meta description, so Google writes its own snippet from whatever text it finds.

  • Title is long (85 characters)

    Your title is 85 characters, so Google will cut it off around 60: “Roger Waters Official Store | Official Store | Roger Waters US Store | Official Store”.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • One H1 headline

    Your <h1> is empty.

  • 37 internal links, 6 external

    The homepage links to 37 pages on shoprogerwaters.com and 6 external pages.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization and WebSite.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

  • XML sitemap found

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

AI search readiness

100
4 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: 4 of 6 facts

    Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.

  • Text is in the HTML

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

  • llms.txt published

    The site publishes https://www.shoprogerwaters.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix68
  • 1 page without a title

    https://www.shoprogerwaters.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

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

  • 6 pages without a meta description

    https://www.shoprogerwaters.com/collections/all, https://www.shoprogerwaters.com/customer_authentication/redirect, https://www.shoprogerwaters.com/policies/shipping-policy, https://www.shoprogerwaters.com/collections/music, https://www.shoprogerwaters.com/collections/merch and https://www.shoprogerwaters.com/collections/home have no meta description, so Google writes the search snippet from whatever text it finds.

  • 13 pages without an H1

    https://www.shoprogerwaters.com/collections/all, https://www.shoprogerwaters.com/customer_authentication/redirect, https://www.shoprogerwaters.com/collections/music, https://www.shoprogerwaters.com/collections/merch, https://www.shoprogerwaters.com/products/roger-waters-this-is-not-a-drill-live-from-prague-4lp and https://www.shoprogerwaters.com/products/roger-waters-the-lockdown-sessions-lp and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 14 internal pages checked

    We fetched 14 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 14 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.

Best practices

2 to fixGoogle 9687
  • 12 small tap targets

    12 of 35 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Uncaught SyntaxError: Unexpected token '}'”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix71
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • Only about 207 words

    The homepage has only about 207 words of visible text; thin pages give Google and first-time buyers little to go on.

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

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SIGN UP”.

  • 1 call to action

    The homepage has 1 call to action, for example “Contact”.

  • 3 short forms

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel (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.

  • 16 cookies set on arrival

    16

    Opening the homepage sets 16 cookies (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.

  • 28 other companies contacted

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

Apps on your store

Your storefront loads 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Geo Pro Geolocation · Klaviyo Email Marketing Sms · Gorgias Live Chat Helpdesk · Easylocation

Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info

Upkeep, stack and company

Stack

Framework
jQuery
E-commerce
Shopify
Analytics
Google Tag Manager
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 32 issues on shoprogerwaters.com, including 17 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