Website review, no card needed

wpshandrails.com logo

wpshandrails.com website review

Visit site (opens in a new tab)Reviewed 8 November 202622 issues · 80 checks

This review found 22 issues worth fixing on wpshandrails.com, 8 of them high impact, across 80 checks. The most urgent: reduce unused JavaScript. 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.5 s1.3 sMay 16Oct 311.3 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.5 s
May 23, 20261.5 s
May 30, 20261.5 s
Jun 6, 20261.4 s
Jun 13, 20261.5 s
Jun 20, 20261.4 s
Jun 27, 20261.4 s
Jul 4, 20261.4 s
Jul 11, 20261.3 s
Jul 18, 20261.3 s
Jul 25, 20261.3 s
Aug 1, 20261.3 s
Aug 8, 20261.3 s
Aug 15, 20261.3 s
Aug 22, 20261.3 s
Aug 29, 20261.4 s
Sep 5, 20261.3 s
Sep 12, 20261.4 s
Sep 19, 20261.4 s
Sep 26, 20261.4 s
Oct 3, 20261.4 s
Oct 10, 20261.4 s
Oct 17, 20261.4 s
Oct 24, 20261.4 s
Oct 31, 20261.3 s
Real-visitor tap response (INP)75th percentile, phones
96 ms85 msMay 16Oct 3195 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202693 ms
May 23, 202695 ms
May 30, 202695 ms
Jun 6, 202691 ms
Jun 13, 202692 ms
Jun 20, 202689 ms
Jun 27, 202688 ms
Jul 4, 202691 ms
Jul 11, 202687 ms
Jul 18, 202687 ms
Jul 25, 202687 ms
Aug 1, 202686 ms
Aug 8, 202687 ms
Aug 15, 202688 ms
Aug 22, 202689 ms
Aug 29, 202692 ms
Sep 5, 202695 ms
Sep 12, 202695 ms
Sep 19, 202695 ms
Sep 26, 202695 ms
Oct 3, 202693 ms
Oct 10, 202695 ms
Oct 17, 202695 ms
Oct 24, 202693 ms
Oct 31, 202695 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 wpshandrails.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. wpshandrails.com at 0.6 s0.6 s
  2. wpshandrails.com at 1.2 s1.2 s
  3. wpshandrails.com at 1.8 s1.8 s
  4. wpshandrails.com at 2.4 s2.4 s
  5. wpshandrails.com at 3.0 s3.0 s
  6. wpshandrails.com at 3.6 s3.6 s
  7. wpshandrails.com at 4.2 s4.2 s
  8. wpshandrails.com at 4.8 s4.8 s

Speed

9 to fix51
  • Reduce unused JavaScript

    1.6 s · 317 KiB

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

  • Main-thread work: 4.3 s

    A phone's processor spends 4.3 s on main-thread work while loading, 2.2 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, Mediahawk and ahrefs.com and others), adding 11.9 MB and 1.3 s of main-thread time.

  • Shopify adds 44 ms

    44 ms

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

  • Mobile performance score: 51

    51/100

    Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.

  • Google Tag Manager adds 913 ms

    913 ms

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

    900 ms

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

  • 12 long tasks on the main thread

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

  • 1,951 HTML elements

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

  • Use efficient cache lifetimes

    150 ms · 76 KiB

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

  • Reduce unused CSS

    150 ms · 35 KiB

    About 35 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.

  • Legacy JavaScript

    150 ms · 21 KiB

    Polyfills for old browsers add 21 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

    154 KiB

    9 images could be 154 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.

  • 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: 6 ms

    6 ms

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

Core Web Vitals

5 to fix100
  • Largest Contentful Paint: 10.5 s

    10.5 s

    Your largest element takes 10.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to enhance your browsing experience, serve p…”.

  • Time to Interactive: 10.8 s

    10.8 s

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

  • Total Blocking Time: 974 ms

    974 ms

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

  • Speed Index: 4.0 s

    4.0 s

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

  • 15 images without width and height

    15 images have no width and height attributes, so the layout jumps as each one loads.

  • Tap response (INP) held steady for real visitors

    0%

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

  • Largest content (LCP) held steady for real visitors

    -9%

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

8 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.3 s

    1.3 s

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

  • Real-user INP: 97 ms

    97 ms

    Real visitors wait 97 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.9 s

    0.9 s

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

  • Real-user TTFB: 530 ms

    530 ms

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix70
  • Page weight: 13.3 MB in 172 requests

    13.3 MB

    Your homepage downloads 13.3 MB in 172 requests on a phone: media 11.1 MB (1), scripts 1,010 KiB (45) and other files 702 KiB (94). Under 2 MB keeps phones on slow connections fast.

  • About 3.8 g of CO₂ per visit

    3.78 g

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

2 to fixGoogle 9697
  • 15 text elements with low contrast

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

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 40 images in the HTML carry an alt attribute.

  • 45 automated accessibility rules passed

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

SEO

1 to fixGoogle 10093
  • Title is long (67 characters)

    Your title is 67 characters, so Google will cut it off around 60: “Balustrades UK | Glass Balustrades Systems for Sale – WPS Handrails”.

  • 171 internal links, 19 external

    The homepage links to 171 pages on wpshandrails.com and 19 external pages.

7 checks passed
  • Meta description: 149 characters

    Your meta description is 149 characters: “WPS Handrails are a leading supplier of glass balustrades & composite decking. Centrally located in the West Midlands, …”.

  • One H1 headline

    Your main headline reads: “WPS Handrails”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: LocalBusiness.

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

  • XML sitemap found

    Your XML sitemap is reachable at https://www.wpshandrails.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: 6 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

3 to fix80
  • 2 pages point its canonical at the homepage

    https://www.wpshandrails.com/pages/shop-balustrades and https://www.wpshandrails.com/pages/framed-glass-balustrades declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

  • 6 pages without a meta description

    https://www.wpshandrails.com/pages/shop-balustrades, https://www.wpshandrails.com/pages/oslo-spigot-glass-balustrade, https://www.wpshandrails.com/pages/glass-button-balustrade, https://www.wpshandrails.com/pages/frameless-glass-parapet-wall, https://www.wpshandrails.com/pages/design-tool and https://www.wpshandrails.com/pages/showroom have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 pages without an H1

    https://www.wpshandrails.com/pages/shop-balustrades, https://www.wpshandrails.com/pages/framed-glass-balustrades, https://www.wpshandrails.com/pages/semi-frameless-glass-balustrades, https://www.wpshandrails.com/pages/frameless-glass-balustrades, https://www.wpshandrails.com/pages/oslo-spigot-glass-balustrade and https://www.wpshandrails.com/pages/wire-balustrades and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 59 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.

  • 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

1 to fixGoogle 10093
  • 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

    29 of 31 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • 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 1,294 words of copy

    The homepage carries about 1,294 words of visible text.

8 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Balustrades” and “Shop Composite Decking”.

  • 21 calls to action

    The homepage has 21 calls to action, for example “Order Free Samples”, “Shop” and “Shop ECOBOARD”.

  • 2 short forms

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

  • Social proof on the page

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

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 1 email link.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • LocalBusiness structured data

    Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.

Privacy and tracking

  • 4 trackers load before any consent

    4

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 6 cookies set on arrival

    6

    Opening the homepage sets 6 cookies, 1 of them by other companies (measured from a US location before any click).

  • 22 other companies contacted

    Loading the homepage contacts 22 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 wpshandrails.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 3 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Instafeed · Xo Gallery · Bs Better Shipping

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

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 22 issues on wpshandrails.com, including 14 speed issues and 1 SEO issue. 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