Website review, no card needed

notonthehighstreet.com logo

notonthehighstreet.com website review

Visit site (opens in a new tab)Reviewed 27 October 202637 issues · 87 checks

This review found 37 issues worth fixing on notonthehighstreet.com, 15 of them high impact, across 87 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.3 s1.2 sMay 9Oct 241.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.3 s
May 16, 20261.3 s
May 23, 20261.3 s
May 30, 20261.3 s
Jun 6, 20261.3 s
Jun 13, 20261.3 s
Jun 20, 20261.3 s
Jun 27, 20261.3 s
Jul 4, 20261.3 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.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.3 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.3 s
Oct 24, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
267 ms230 msMay 9Oct 24249 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026263 ms
May 16, 2026261 ms
May 23, 2026260 ms
May 30, 2026260 ms
Jun 6, 2026258 ms
Jun 13, 2026254 ms
Jun 20, 2026252 ms
Jun 27, 2026253 ms
Jul 4, 2026254 ms
Jul 11, 2026257 ms
Jul 18, 2026260 ms
Jul 25, 2026254 ms
Aug 1, 2026245 ms
Aug 8, 2026237 ms
Aug 15, 2026235 ms
Aug 22, 2026238 ms
Aug 29, 2026245 ms
Sep 5, 2026247 ms
Sep 12, 2026245 ms
Sep 19, 2026239 ms
Sep 26, 2026234 ms
Oct 3, 2026235 ms
Oct 10, 2026238 ms
Oct 17, 2026244 ms
Oct 24, 2026249 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 notonthehighstreet.com (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. notonthehighstreet.com at 1.1 s1.1 s
  2. notonthehighstreet.com at 2.2 s2.2 s
  3. notonthehighstreet.com at 3.4 s3.4 s
  4. notonthehighstreet.com at 4.5 s4.5 s
  5. notonthehighstreet.com at 5.6 s5.6 s
  6. notonthehighstreet.com at 6.7 s6.7 s
  7. notonthehighstreet.com at 7.8 s7.8 s
  8. notonthehighstreet.com at 9.0 s9.0 s

Speed

9 to fix35
  • Reduce unused JavaScript

    3.5 s · 965 KiB

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

  • Improve image delivery

    1.6 s · 1.4 MB

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

  • Google Tag Manager adds 1.2 s

    1.2 s

    Google Tag Manager costs a phone 1.2 s of main-thread work and 568 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

  • Mobile performance score: 35

    35/100

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

  • Main-thread work: 5.9 s

    A phone's processor spends 5.9 s on main-thread work while loading, 3.6 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, Optanon and Usabilla and others), adding 803 KiB and 1.4 s of main-thread time.

  • 20 long tasks on the main thread

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

  • Legacy JavaScript

    300 ms · 30 KiB

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

  • 2,429 HTML elements

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

  • Use efficient cache lifetimes

    250 ms · 79 KiB

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

  • Render-blocking requests

    50 ms

    1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 50 ms.

  • Reduce unused CSS

    15 KiB

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

  • Duplicated JavaScript

    1 KiB

    1 KiB JavaScript is shipped twice across bundles.

1 checks passed
  • Server response: 26 ms

    26 ms

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

Core Web Vitals

8 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: 23.4 s

    23.4 s

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

  • Time to Interactive: 27.6 s

    27.6 s

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

  • Speed Index: 14.3 s

    14.3 s

    Visually, the page fills in at 14.3 s (Speed Index). Good is under 3.4 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.

  • Real-user INP: 317 ms

    317 ms

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

  • First Contentful Paint: 2.4 s

    2.4 s

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

  • 4 images without width and height

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

  • Tap response (INP) held steady for real visitors

    -6%

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

5 checks passed
  • 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 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.1 s

    1.1 s

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

  • Real-user TTFB: 374 ms

    374 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

4 to fix45
  • Page weight: 5.5 MB in 300 requests

    5.5 MB

    Your homepage downloads 5.5 MB in 300 requests on a phone: scripts 2.6 MB (49), images 2.6 MB (85) and fonts 111 KiB (7). Under 2 MB keeps phones on slow connections fast.

  • 1 image over 500 KB

    StandardBanner.gif weighs 1.4 MB. On a phone connection a single image that size takes seconds.

  • An image on the first screen is lazy-loaded

    hero_mob_app_food_hall2.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 far larger than shown

    77 KiB

    1 image is downloaded at several times the size a phone draws it, for example link_block_personalised.jpg at 857 px wide, shown at 157 px. Resized copies would save about 77 KiB.

  • 10 images in older formats

    10 images (464 KiB) are 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.

  • 2 images below the first screen load straight away

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

  • About 1.6 g of CO₂ per visit

    1.56 g

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

Accessibility

7 to fixGoogle 8992
  • Malformed lists

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

  • 49 images without alt text

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

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

  • All page content should be contained by landmarks (1 element)

    All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

  • ARIA role should be appropriate for the element (60 elements)

    ARIA role should be appropriate for the element: 60 elements on the page fail this check, rated minor by axe-core.

  • 40 links without text

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

  • 1 form field without a label

    1 form field has no label, so screen readers announce an empty box and autofill guesses.

1 checks passed
  • 51 automated accessibility rules passed

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

SEO

4 to fixGoogle 8586
  • 2 H1 headlines

    There are 2 <h1> headlines (“Unique & Personalised Gifts Shop” and “Countdown to Christmas”). One clear main headline is easier for people and search engines.

  • 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 XML sitemap

    No XML sitemap at https://www.notonthehighstreet.com/feeds/sitemaps/sitemap.xml.gz, so Google discovers your pages only by following links.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • No X (Twitter) card tag

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

  • 858 internal links, 20 external

    The homepage links to 858 pages on notonthehighstreet.com and 20 external pages.

5 checks passed
  • Meta description: 148 characters

    Your meta description is 148 characters: “Discover thousands of unique finds at Not on The High Street. From gifts to homeware, they’re all made or sourced by th…”.

  • Title: 42 characters

    Your title is a healthy 42 characters: “NOTHS | Shop Gifts, Jewellery, Home & More”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

  • robots.txt in place

    robots.txt is in place and points crawlers to your sitemap.

AI search readiness

100
  • No llms.txt

    There is no https://www.notonthehighstreet.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

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.

  • Text is in the HTML

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

Other pages

2 to fix88
  • 1 linked page hidden from search

    https://www.notonthehighstreet.com/sale/experiences-sale is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.

  • 3 pages without a meta description

    https://www.notonthehighstreet.com/sale/view-all-sale-items, https://www.notonthehighstreet.com/sale/experiences-sale and https://www.notonthehighstreet.com/sale/hobbies-leisure-sale have no meta description, so Google writes the search snippet from whatever text it finds.

  • 15 internal pages checked

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

  • Every page has an H1

    Each page we checked has a main headline.

  • Every page has a title

    All 15 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9278
  • 2 broken images

    2 images failed to load on a phone, for example https://bat.bing.net/action/0?ti=5510623&tm=gtm002&Ver=2&mid=f392e9cc-d93a-4a0c-b0fa-1f688fb2c0bb&bo=2&pi=918639831&lg=en-US&sw=390&sh=844&sc=24&nwd=1&tl=NOTHS%20%7C%20Shop%20Gifts,%20Jewellery,%20Hom.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 403 ()”.

  • Missing source maps

    Large scripts ship without source maps.

  • Browser-reported issues

    Chrome logged issues while loading the page (“Content security policy”).

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

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

  • About 1,600 words of copy

    The homepage carries about 1,600 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 birthday gifts”.

  • 21 calls to action

    The homepage has 21 calls to action, for example “Book lovers”, “The Flower Shop” and “Shop the most creative advent calendars”.

  • 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: 1 customer or partner logo, a star rating and 2 trust badges.

  • Analytics in place

    Analytics detected: Google Tag Manager.

  • Risk reducer mentioned

    A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.

Privacy and tracking

  • 3 trackers load before any consent

    3

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

  • 11 cookies set on arrival

    11

    Opening the homepage sets 11 cookies (measured from a US location before any click).

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

1 checks passed
  • Consent tool: OneTrust

    A consent management tool (OneTrust) 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 notonthehighstreet.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.

Upkeep, stack and company

Stack

Framework
Next.js
Analytics
Google Tag Manager
Hosting
Cloudflare

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 37 issues on notonthehighstreet.com, including 17 speed issues, 4 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