Website review, no card needed

ohlaura.co.uk logo

ohlaura.co.uk website review

Visit site (opens in a new tab)Reviewed 9 November 202624 issues · 77 checks

This review found 24 issues worth fixing on ohlaura.co.uk, 5 of them high impact, across 77 checks. The most urgent: 22 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
1.7 s544 msMay 23Nov 7701 ms
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.6 s
May 30, 20261.3 s
Jun 6, 20261.2 s
Jun 13, 20261.2 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 2026956 ms
Jul 18, 20261.0 s
Jul 25, 2026930 ms
Aug 1, 2026867 ms
Aug 8, 2026808 ms
Aug 15, 2026831 ms
Aug 22, 2026889 ms
Aug 29, 2026861 ms
Sep 5, 2026885 ms
Sep 12, 2026892 ms
Sep 19, 2026848 ms
Sep 26, 2026814 ms
Oct 3, 2026706 ms
Oct 10, 2026687 ms
Oct 17, 2026694 ms
Oct 24, 2026682 ms
Oct 31, 2026703 ms
Nov 7, 2026701 ms
Real-visitor tap response (INP)75th percentile, phones
97 ms77 msMay 23Nov 786 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202688 ms
May 30, 202679 ms
Jun 6, 202682 ms
Jun 13, 202681 ms
Jun 20, 202684 ms
Jun 27, 202687 ms
Jul 4, 202688 ms
Jul 11, 202695 ms
Jul 18, 202689 ms
Jul 25, 202687 ms
Aug 1, 202686 ms
Aug 8, 202686 ms
Aug 15, 202682 ms
Aug 22, 202682 ms
Aug 29, 202679 ms
Sep 5, 202682 ms
Sep 12, 202687 ms
Sep 19, 202685 ms
Sep 26, 202685 ms
Oct 3, 202679 ms
Oct 10, 202679 ms
Oct 17, 202679 ms
Oct 24, 202682 ms
Oct 31, 202686 ms
Nov 7, 202686 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 ohlaura.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. ohlaura.co.uk at 0.6 s0.6 s
  2. ohlaura.co.uk at 1.2 s1.2 s
  3. ohlaura.co.uk at 1.8 s1.8 s
  4. ohlaura.co.uk at 2.4 s2.4 s
  5. ohlaura.co.uk at 3.0 s3.0 s
  6. ohlaura.co.uk at 3.6 s3.6 s
  7. ohlaura.co.uk at 4.1 s4.1 s
  8. ohlaura.co.uk at 4.7 s4.7 s

Speed

4 to fix75
  • Mobile performance score: 75

    75/100

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

  • Render-blocking requests

    600 ms

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

  • Main-thread work: 2.2 s

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

  • 1,656 HTML elements

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Shopify, cloudfront.net and nfcube.com and others), adding 402 KiB and 231 ms of main-thread time.

  • Improve image delivery

    227 KiB

    10 images could be 227 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Reduce unused JavaScript

    150 ms · 70 KiB

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

  • Use efficient cache lifetimes

    79 KiB

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

  • 4 long tasks on the main thread

    4 long tasks block the main thread while loading, the longest for 67 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.

  • Legacy JavaScript

    9 KiB

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

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

  • Duplicated JavaScript

    5 KiB

    5 KiB JavaScript is shipped twice across bundles.

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

    9 ms

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

Core Web Vitals

3 to fix100
  • Largest Contentful Paint: 10.8 s

    10.8 s

    Your largest element takes 10.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “stationery designed for neurodivergent and busy brains SHOP…”.

  • Time to Interactive: 11.0 s

    11.0 s

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

  • 47 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +3%

    Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 88 ms to 86 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.7 s

    1.7 s

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

  • Real-user INP: 113 ms

    113 ms

    Real visitors wait 113 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: 1.2 s

    1.2 s

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

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

    -52%

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

  • Speed Index: 2.8 s

    2.8 s

    Visually, the page fills in at 2.8 s (Speed Index), inside the 3.4 s “good” threshold.

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

    0.004

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

  • Total Blocking Time: 20 ms

    20 ms

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

Images and page weight

2 to fix75
  • Page weight: 3.4 MB in 212 requests

    3.4 MB

    Your homepage downloads 3.4 MB in 212 requests on a phone: images 2.0 MB (31), other files 745 KiB (83) and scripts 459 KiB (63). Under 2 MB keeps phones on slow connections fast.

  • 1 image far larger than shown

    68 KiB

    1 image is downloaded at several times the size a phone draws it, for example little_sketchy_logo_931dbc6b-0c65-4ca5-b4c1-b2b1e8ce9f68.png at 500 px wide, shown at 86 px. Resized copies would save about 68 KiB.

  • 2 images below the first screen load straight away

    2 images further down the page (117 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 1.0 g of CO₂ per visit

    0.96 g

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

4 to fixGoogle 8893
  • 22 text elements with low contrast

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

  • Hidden but focusable

    15 elements hidden from screen readers can still receive keyboard focus.

  • 51 images without alt text

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

  • Headings should not be empty (2 elements)

    Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

SEO

4 to fixGoogle 8581
  • Title is short (20 characters)

    Your title is only 20 characters: “Oh, Laura – Oh Laura”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“” and “stationery designed for neurodivergent and busy b…”). One clear main headline is easier for people and search engines.

  • Meta description is long (170 characters)

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

  • 4 links crawlers can't follow

    4 links have no real href, so search engines can't follow them.

  • 165 internal links, 8 external

    The homepage links to 165 pages on ohlaura.co.uk and 8 external pages.

5 checks passed
  • Canonical URL set

    The canonical URL is https://ohlaura.co.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://ohlaura.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: 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 (1,136 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

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

Other pages

1 to fix95
  • 15 pages without a meta description

    https://ohlaura.co.uk/collections/all, https://ohlaura.co.uk/collections/new-in-1, https://ohlaura.co.uk/collections/stationery, https://ohlaura.co.uk/collections/bookmarks, https://ohlaura.co.uk/collections/cards and https://ohlaura.co.uk/collections/keyboard-planners and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 pages slow to respond

    https://ohlaura.co.uk/collections/all, https://ohlaura.co.uk/collections/stationery and https://ohlaura.co.uk/collections/bookmarks took over 3 s to send their HTML from our server.

  • 15 internal pages checked

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

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

2 to fixGoogle 9687
  • 46 small tap targets

    46 of 63 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 “Cannot read properties of undefined (reading 'className')”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix75
  • Thin social proof

    Social proof on the homepage: 19 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

    The homepage carries about 485 words of visible text.

3 checks passed
  • Clear next step on the first screen

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

  • 18 calls to action

    The homepage has 18 calls to action, for example “Shop All”, “Contact” and “Apply For a Wholesale Account”.

  • 15 short forms

    15 short forms (2 fields at most) are right on the homepage, asking for an email.

Privacy and tracking

1 to fix
  • 5 trackers load before any consent

    5

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

  • 15 other companies contacted

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

Upkeep, stack and company

Stack

E-commerce
Shopify;Shopify Plus
Hosting
Shopify

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 24 issues on ohlaura.co.uk, including 7 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