Website review, no card needed

yellowpop.co.uk logo

yellowpop.co.uk website review

Visit site (opens in a new tab)Reviewed 10 November 202643 issues · 89 checks

This review found 43 issues worth fixing on yellowpop.co.uk, 19 of them high impact, across 89 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

Full-page screenshot of yellowpop.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. yellowpop.co.uk at 1.0 s1.0 s
  2. yellowpop.co.uk at 1.9 s1.9 s
  3. yellowpop.co.uk at 2.9 s2.9 s
  4. yellowpop.co.uk at 3.8 s3.8 s
  5. yellowpop.co.uk at 4.8 s4.8 s
  6. yellowpop.co.uk at 5.8 s5.8 s
  7. yellowpop.co.uk at 6.7 s6.7 s
  8. yellowpop.co.uk at 7.7 s7.7 s

Speed

11 to fix30
  • Reduce unused JavaScript

    1.5 s · 1.3 MB

    About 1.3 MB 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.

  • Render-blocking requests

    1.6 s

    17 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.

  • Mobile performance score: 30

    30/100

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

  • Main-thread work: 7.7 s

    A phone's processor spends 7.7 s on main-thread work while loading, 4.1 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 (hsappstatic.net, Google CDN and Google Tag Manager and others), adding 2.0 MB and 2.1 s of main-thread time.

  • Improve image delivery

    1.8 MB

    17 images could be 1.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • hsappstatic.net adds 887 ms

    887 ms

    hsappstatic.net costs a phone 887 ms of main-thread work and 718 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.

  • Use efficient cache lifetimes

    640 KiB

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

  • Google CDN adds 455 ms

    455 ms

    Google CDN costs a phone 455 ms of main-thread work and 775 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.

  • 20 long tasks on the main thread

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

  • 2,816 HTML elements

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

  • Reduce unused CSS

    150 ms · 89 KiB

    About 89 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

    100 ms · 88 KiB

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

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • Minify JavaScript

    28 KiB

    28 KiB could be saved by minifying JavaScript.

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

    16 ms

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

Core Web Vitals

7 to fix26
  • Time to Interactive: 32.7 s

    32.7 s

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

  • Largest Contentful Paint: 7.1 s

    7.1 s

    Your largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “4.9 (1600+ ratings) LIGHTEN UP YOUR SPACE WITH A LED NEON S…”.

  • Total Blocking Time: 1.9 s

    1.9 s

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

  • Speed Index: 7.5 s

    7.5 s

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

  • Cumulative Layout Shift: 0.193

    0.193

    The layout shifts by 0.193 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • First Contentful Paint: 2.3 s

    2.3 s

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

  • 2 images without width and height

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

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Images and page weight

4 to fix28
  • Page weight: 18.5 MB in 309 requests

    18.5 MB

    Your homepage downloads 18.5 MB in 309 requests on a phone: media 9.3 MB (5), images 4.6 MB (106) and scripts 3.1 MB (95). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    popbox-visual-barking-dog-1.jpg weighs 842 KiB. On a phone connection a single image that size takes seconds.

  • 5 images far larger than shown

    1.0 MB

    5 images are downloaded at several times the size a phone draws them, for example popbox-visual-barking-dog-1.jpg at 4,156 px wide, shown at 390 px. Resized copies would save about 1.0 MB.

  • 15 images below the first screen load straight away

    15 images further down the page (2.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 5.2 g of CO₂ per visit

    5.24 g

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

1 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

Accessibility

10 to fixGoogle 6887
  • 19 buttons without a name

    19 buttons have no accessible name, so screen readers announce just “button”.

  • ARIA roles used must conform to valid values (1 element)

    ARIA roles used must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

  • Orphan list items

    Some list items are not inside a list.

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 30 images without alt text

    30 images have no alt text, which hurts accessibility and image search.

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 17 links without text

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

  • 4 form fields without a label

    4 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • Elements with visible text labels do not have matching accessible names.

    Elements with visible text labels do not have matching accessible names. (4 elements).

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

2 to fixGoogle 8583
  • No meta description

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

  • Title is short (12 characters)

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

  • 264 internal links, 20 external

    The homepage links to 264 pages on yellowpop.co.uk and 20 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “LIGHTEN UP YOUR SPACE WITH A LED NEON SIGN LIGHTEN UP YOUR SPACE WITH A LED NEON SIGN”.

  • Canonical URL set

    The canonical URL is https://yellowpop.co.uk/.

  • Structured data in place

    Structured data found: BreadcrumbList, 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://yellowpop.co.uk/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: 5 of 6 facts

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

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix90
  • 10 pages without a meta description

    https://yellowpop.co.uk/collections/popbox, https://yellowpop.co.uk/collections/neon-collabs, https://yellowpop.co.uk/collections/new-neon-collabs, https://yellowpop.co.uk/collections/kenny-scharf, https://yellowpop.co.uk/collections/jean-michel-basquiat and https://yellowpop.co.uk/collections/andy-warhol and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 8 pages without an H1

    https://yellowpop.co.uk/collections/neon-collabs, https://yellowpop.co.uk/collections/new-neon-collabs, https://yellowpop.co.uk/collections/neon-best-sellers, https://yellowpop.co.uk/collections/ready-to-ship, https://yellowpop.co.uk/collections/jean-michel-basquiat and https://yellowpop.co.uk/collections/andy-warhol and 2 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 80 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 to fixGoogle 5474
  • 1 broken image

    1 image failed to load on a phone, for example https://bat.bing.net/action/0?ti=17532556&tm=gtm002&Ver=2&mid=af8dd531-1202-4958-bad4-23a2ce56fe2b&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=YELLOWPOP%20UK&p=https%3A%2F%2Fyellowpop.co.u.

  • 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 third-party cookie

    1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Cookie”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix88
  • 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 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,534 words of copy

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop all” and “Get A Free Quote 24HRS”.

  • 27 calls to action

    The homepage has 27 calls to action, for example “Shop all”, “Get A Free Quote 24HRS” and “Get free quote in 24h”.

  • 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: 3 testimonial or review blocks, 10 customer or partner logos and “Join 100,000+ happy customers”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

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

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 cookies, 5 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.

  • 50 other companies contacted

    Loading the homepage contacts 50 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 yellowpop.co.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 10 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Consentmo Gdpr · Cozy Country Redirect · Klaviyo Email Marketing Sms · Seowill Redirects · Gdpr Backpack · Xo Gallery · rakuten.com · rise-ai.com · addons.business · amazonaws.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

Framework
Tailwind CSS
E-commerce
Shopify
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 43 issues on yellowpop.co.uk, including 18 speed issues, 2 SEO issues and 2 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