Website review, no card needed

justlyne.co.uk logo

justlyne.co.uk website review

Visit site (opens in a new tab)Reviewed 12 November 202633 issues · 82 checks

This review found 33 issues worth fixing on justlyne.co.uk, 10 of them high impact, across 82 checks. The most urgent: improve image delivery. 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
3.0 s1.6 sMay 23Nov 72.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.3 s
Jun 13, 20262.2 s
Jun 20, 20262.3 s
Jul 4, 20262.8 s
Sep 19, 20261.7 s
Oct 17, 20261.8 s
Oct 24, 20262.0 s
Oct 31, 20262.4 s
Nov 7, 20262.2 s

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 justlyne.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. justlyne.co.uk at 0.7 s0.7 s
  2. justlyne.co.uk at 1.3 s1.3 s
  3. justlyne.co.uk at 2.0 s2.0 s
  4. justlyne.co.uk at 2.7 s2.7 s
  5. justlyne.co.uk at 3.3 s3.3 s
  6. justlyne.co.uk at 4.0 s4.0 s
  7. justlyne.co.uk at 4.6 s4.6 s
  8. justlyne.co.uk at 5.3 s5.3 s

Speed

8 to fix69
  • Improve image delivery

    3.3 s · 2.5 MB

    31 images could be 2.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.3 s faster on a phone.

  • Render-blocking requests

    1.1 s

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

  • Mobile performance score: 69

    69/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (Klaviyo, JSDelivr CDN and Shopify and others), adding 2.3 MB and 552 ms of main-thread time.

  • Reduce unused JavaScript

    300 ms · 322 KiB

    About 322 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

  • Shopify adds 89 ms

    89 ms

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

  • Main-thread work: 2.6 s

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

  • 1,889 HTML elements

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

  • 5 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Use efficient cache lifetimes

    62 KiB

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

  • Legacy JavaScript

    54 KiB

    Polyfills for old browsers add 54 KiB JavaScript that modern phones do not need.

  • Reduce unused CSS

    16 KiB

    About 16 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.

1 checks passed
  • Server response: 14 ms

    14 ms

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

Core Web Vitals

5 to fix67
  • 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: 22.2 s

    22.2 s

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

  • Time to Interactive: 23.0 s

    23.0 s

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

  • Real-user CLS: 0.24

    0.24

    For real visitors the layout shifts by 0.24 (75th percentile). Good is under 0.1.

  • Speed Index: 5.4 s

    5.4 s

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

  • Largest content (LCP) held steady for real visitors

    0%

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

7 checks passed
  • Real-user LCP: 2.3 s

    2.3 s

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

  • Real-user INP: 110 ms

    110 ms

    Real visitors wait 110 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user FCP: 1.0 s

    1.0 s

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

  • Real-user TTFB: 430 ms

    430 ms

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

  • Total Blocking Time: 145 ms

    145 ms

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

  • First Contentful Paint: 1.2 s

    1.2 s

    The first text or image appears after 1.2 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

3 to fix42
  • Page weight: 6.8 MB in 244 requests

    6.8 MB

    Your homepage downloads 6.8 MB in 244 requests on a phone: images 4.9 MB (50), scripts 904 KiB (89) and other files 803 KiB (89). Under 2 MB keeps phones on slow connections fast.

  • 6 images far larger than shown

    497 KiB

    6 images are downloaded at several times the size a phone draws them, for example shibainu_kiwii-1.red.jpg at 1,200 px wide, shown at 80 px. Resized copies would save about 497 KiB.

  • An image on the first screen is lazy-loaded

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

  • 1 image in older formats

    1 image (238 KiB) 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 1.9 g of CO₂ per visit

    1.92 g

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

Accessibility

6 to fixGoogle 8590
  • Scrollable region must have keyboard access (2 elements)

    Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

  • Elements must only use permitted ARIA attributes (1 element)

    Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

  • 88 images without alt text

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

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

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

  • 3 links without text

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

  • Alternative text of images should not be repeated as text (4 elements)

    Alternative text of images should not be repeated as text: 4 elements on the page fail this check, rated minor by axe-core.

  • Headings skip levels

    Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.

1 checks passed
  • 39 automated accessibility rules passed

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

SEO

5 to fixGoogle 9276
  • Title is long (66 characters)

    Your title is 66 characters, so Google will cut it off around 60: “🥇 Just Lyne - Custom One Line art - Best Gift for your Loved Ones”.

  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • 4 H1 headlines

    There are 4 <h1> headlines (“How it works?”, “A Piece of Your Pet, Forever” and “Experience the Joy of Unwrapping”). One clear main headline is easier for people and search engines.

  • Meta description is long (190 characters)

    Your meta description is 190 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No social preview image

    No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • No X (Twitter) card tag

    No twitter:card tag. X falls back to Open Graph, which is incomplete here.

  • 114 internal links, 8 external

    The homepage links to 114 pages on justlyne.co.uk and 8 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://justlyne.com/.

  • 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://justlyne.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.

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.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

2 to fix93
  • 10 pages share a meta description

    https://justlyne.com/collections/best-sellers-new, https://justlyne.com/collections/all-products, https://justlyne.com/products/kids-custom-hoodie, https://justlyne.com/products/custom-mug, https://justlyne.com/products/christmas-ornament and https://justlyne.com/pages/faqs and 4 others use the same meta description. A description written for each page earns more clicks.

  • 5 pages without an H1

    https://justlyne.com/collections/all-products, https://justlyne.com/products/custom-one-line-hoodie, https://justlyne.com/products/custom-embroidered-sweatshirt, https://justlyne.com/products/custom-one-line-art and https://justlyne.com/pages/contact-us have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://justlyne.com/collections/all-products has 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 26 found) and read each the way a search engine does.

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

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

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

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

1 to fix90
  • No analytics detected

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

  • No form on the homepage

    There is no form on the homepage, so every lead has to click through to another page first.

  • 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 525 words of copy

    The homepage carries about 525 words of visible text.

4 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Shop Best Sellers” and “Order Status”.

  • 21 calls to action

    The homepage has 21 calls to action, for example “Shop Hoodies”, “Order Status” and “Contact Us”.

  • Social proof on the page

    Social proof on the homepage: 9 testimonial or review blocks, a star rating, 3 trust badges and “180,000+ Happy customers”.

  • Direct contact links

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

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.

  • 23 cookies set on arrival

    23

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

  • 32 other companies contacted

    Loading the homepage contacts 32 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 justlyne.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 9 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Triplewhale · Lyne Testing · Candy Rack · Klaviyo Email Marketing Sms · Upload Lift · Aftersell · richpanel.com · socialsnowball.io · loox.io

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

CMS
adastra
Framework
Tailwind CSS
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 33 issues on justlyne.co.uk, including 13 speed issues, 5 SEO issues and 1 conversion gap. 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