Website review, no card needed

shoyoroll.uk logo

shoyoroll.uk website review

Visit site (opens in a new tab)Reviewed 13 November 202623 issues · 73 checks

This review found 23 issues worth fixing on shoyoroll.uk, 5 of them high impact, across 73 checks. The most urgent: 9 text elements with low contrast. 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
927 ms729 msMay 23Nov 7759 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 2026872 ms
May 30, 2026833 ms
Jun 6, 2026813 ms
Jun 13, 2026868 ms
Jun 20, 2026864 ms
Jun 27, 2026868 ms
Jul 4, 2026890 ms
Jul 11, 2026873 ms
Jul 18, 2026866 ms
Jul 25, 2026854 ms
Aug 1, 2026819 ms
Aug 8, 2026850 ms
Aug 15, 2026879 ms
Aug 22, 2026902 ms
Aug 29, 2026904 ms
Sep 5, 2026884 ms
Sep 12, 2026866 ms
Sep 19, 2026832 ms
Sep 26, 2026828 ms
Oct 3, 2026774 ms
Oct 10, 2026752 ms
Oct 17, 2026764 ms
Oct 24, 2026765 ms
Oct 31, 2026758 ms
Nov 7, 2026759 ms
Real-visitor tap response (INP)75th percentile, phones
81 ms68 msMay 23Nov 772 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202679 ms
May 30, 202679 ms
Jun 6, 202678 ms
Jun 13, 202679 ms
Jun 20, 202678 ms
Jun 27, 202678 ms
Jul 4, 202678 ms
Jul 11, 202678 ms
Jul 18, 202677 ms
Jul 25, 202674 ms
Aug 1, 202671 ms
Aug 8, 202673 ms
Aug 15, 202677 ms
Aug 22, 202675 ms
Aug 29, 202671 ms
Sep 5, 202670 ms
Sep 12, 202670 ms
Sep 19, 202671 ms
Sep 26, 202672 ms
Oct 3, 202669 ms
Oct 10, 202669 ms
Oct 17, 202670 ms
Oct 24, 202670 ms
Oct 31, 202671 ms
Nov 7, 202672 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 shoyoroll.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. shoyoroll.uk at 0.7 s0.7 s
  2. shoyoroll.uk at 1.5 s1.5 s
  3. shoyoroll.uk at 2.2 s2.2 s
  4. shoyoroll.uk at 2.9 s2.9 s
  5. shoyoroll.uk at 3.7 s3.7 s
  6. shoyoroll.uk at 4.4 s4.4 s
  7. shoyoroll.uk at 5.2 s5.2 s
  8. shoyoroll.uk at 5.9 s5.9 s

Speed

5 to fix74
  • Mobile performance score: 74

    74/100

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

  • Render-blocking requests

    650 ms

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

  • Improve image delivery

    450 ms · 177 KiB

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

  • Use efficient cache lifetimes

    260 KiB

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

  • Shopify adds 123 ms

    123 ms

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Shopify, Mailchimp and kiwisizing.com and others), adding 762 KiB and 242 ms of main-thread time.

  • Reduce unused JavaScript

    232 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 69 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    12 KiB

    About 12 KiB of CSS is downloaded but never applied on this page.

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

  • Minify JavaScript

    3 KiB

    3 KiB could be saved by minifying JavaScript.

2 checks passed
  • Main-thread work: 1.5 s

    A phone's processor spends 1.5 s on main-thread work while loading, 520 ms of it running JavaScript. That is comfortably low.

  • Server response: 25 ms

    25 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 6.5 s

    6.5 s

    Your largest element takes 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • Time to Interactive: 12.1 s

    12.1 s

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

  • Speed Index: 4.6 s

    4.6 s

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

  • Tap response (INP) held steady for real visitors

    -9%

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

10 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.0 s

    1.0 s

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

  • Real-user INP: 95 ms

    95 ms

    Real visitors wait 95 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: 261 ms

    261 ms

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

  • Largest content (LCP) got 11% faster for real visitors

    -11%

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

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

  • Total Blocking Time: 10 ms

    10 ms

    Scripts block the page for only 10 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix81
  • Page weight: 2.9 MB in 275 requests

    2.9 MB

    Your homepage downloads 2.9 MB in 275 requests on a phone: images 1.2 MB (24), scripts 797 KiB (122) and other files 696 KiB (96). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    1STORE_BANNER_copy_87e71ee8-8c6c-4acf-a326-76793cce81a1.jpg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

  • About 0.8 g of CO₂ per visit

    0.83 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • 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 9797
  • 9 text elements with low contrast

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

2 checks passed
  • Every image has alt text

    All 24 images in the HTML carry an alt attribute.

  • 50 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: 50 passed and 2 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

2 to fixGoogle 10088
  • Title is short (12 characters)

    Your title is only 12 characters: “Shoyoroll UK”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • One H1 headline

    Your <h1> is empty.

  • 50 internal links, 1 external

    The homepage links to 50 pages on shoyoroll.uk and 1 external page.

6 checks passed
  • Meta description: 134 characters

    Your meta description is 134 characters: “Our Apparel & Goods Shoyoroll is a uniform and apparel supply company that is dedicated to the finest fit and quality o…”.

  • Canonical URL set

    The canonical URL is https://www.shoyoroll.uk/.

  • Structured data in place

    Structured data found: Organization and WebSite.

  • 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.shoyoroll.uk/sitemap.xml.

AI search readiness

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

  • llms.txt published

    The site publishes https://www.shoyoroll.uk/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.shoyoroll.uk/customer_authentication/redirect has no <title>, so Google invents the link text in results.

  • 1 linked page hidden from search

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

  • 11 pages without a meta description

    https://www.shoyoroll.uk/collections/all, https://www.shoyoroll.uk/customer_authentication/redirect, https://www.shoyoroll.uk/collections/kimonos, https://www.shoyoroll.uk/collections/no-gi, https://www.shoyoroll.uk/collections/apparel and https://www.shoyoroll.uk/collections/accessories and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 7 pages without an H1

    https://www.shoyoroll.uk/collections/all, https://www.shoyoroll.uk/customer_authentication/redirect, https://www.shoyoroll.uk/collections/kimonos, https://www.shoyoroll.uk/collections/no-gi, https://www.shoyoroll.uk/collections/apparel and https://www.shoyoroll.uk/collections/accessories and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 2 pages with very little text

    https://www.shoyoroll.uk/pages/the-kimono and https://www.shoyoroll.uk/pages/contact have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

  • 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

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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 analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • 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 121 words

    The homepage has only about 121 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.

3 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “SHOP NOW”.

  • 25 calls to action

    The homepage has 25 calls to action, for example “SHOP”, “SHOP NOW” and “Contact”.

  • 4 short forms

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

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 13 cookies set on arrival

    13

    Opening the homepage sets 13 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.

  • 21 other companies contacted

    Loading the homepage contacts 21 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 shoyoroll.uk, 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 7 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Gempages Builder · Gsc Countdown Timer · amazonaws.com · chimpstatic.com · herokuapp.com · nfcube.com · kiwisizing.com

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
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 23 issues on shoyoroll.uk, including 8 speed issues, 2 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

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