Website review, no card needed

instantprint.co.uk logo

instantprint.co.uk website review

Visit site (opens in a new tab)Reviewed 28 October 202637 issues · 92 checks

This review found 37 issues worth fixing on instantprint.co.uk, 16 of them high impact, across 92 checks. The most urgent: render-blocking requests. 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.6 s1.2 sMay 9Oct 241.2 s
Show as table
DateReal-visitor load time (LCP)
May 9, 20261.6 s
May 16, 20261.6 s
May 23, 20261.6 s
May 30, 20261.6 s
Jun 6, 20261.6 s
Jun 13, 20261.6 s
Jun 20, 20261.6 s
Jun 27, 20261.6 s
Jul 4, 20261.6 s
Jul 11, 20261.6 s
Jul 18, 20261.6 s
Jul 25, 20261.5 s
Aug 1, 20261.5 s
Aug 8, 20261.4 s
Aug 15, 20261.4 s
Aug 22, 20261.3 s
Aug 29, 20261.3 s
Sep 5, 20261.2 s
Sep 12, 20261.2 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.3 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.2 s
Real-visitor tap response (INP)75th percentile, phones
184 ms126 msMay 9Oct 24175 ms
Show as table
DateReal-visitor tap response (INP)
May 9, 2026177 ms
May 16, 2026175 ms
May 23, 2026175 ms
May 30, 2026176 ms
Jun 6, 2026175 ms
Jun 13, 2026173 ms
Jun 20, 2026172 ms
Jun 27, 2026173 ms
Jul 4, 2026173 ms
Jul 11, 2026173 ms
Jul 18, 2026172 ms
Jul 25, 2026163 ms
Aug 1, 2026158 ms
Aug 8, 2026153 ms
Aug 15, 2026146 ms
Aug 22, 2026144 ms
Aug 29, 2026139 ms
Sep 5, 2026136 ms
Sep 12, 2026133 ms
Sep 19, 2026142 ms
Sep 26, 2026153 ms
Oct 3, 2026163 ms
Oct 10, 2026173 ms
Oct 17, 2026177 ms
Oct 24, 2026175 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 instantprint.co.uk (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. instantprint.co.uk at 0.4 s0.4 s
  2. instantprint.co.uk at 0.8 s0.8 s
  3. instantprint.co.uk at 1.2 s1.2 s
  4. instantprint.co.uk at 1.6 s1.6 s
  5. instantprint.co.uk at 2.0 s2.0 s
  6. instantprint.co.uk at 2.4 s2.4 s
  7. instantprint.co.uk at 2.8 s2.8 s
  8. instantprint.co.uk at 3.2 s3.2 s

Speed

10 to fix15
  • Render-blocking requests

    3.8 s

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

  • Reduce unused JavaScript

    1.1 s · 529 KiB

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

  • Mobile performance score: 15

    15/100

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

  • 8 third-party services on the page

    8 third-party services load with your homepage (cloudfront.net, Google Tag Manager and Insider and others), adding 2.9 MB and 1.7 s of main-thread time.

  • Use efficient cache lifetimes

    650 ms · 1.1 MB

    40 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

  • cloudfront.net adds 655 ms

    655 ms

    cloudfront.net costs a phone 655 ms of main-thread work and 1.5 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.

  • Google Tag Manager adds 555 ms

    555 ms

    Google Tag Manager costs a phone 555 ms of main-thread work and 740 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.

  • Insider adds 351 ms

    351 ms

    Insider costs a phone 351 ms of main-thread work and 489 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.

  • Main-thread work: 3.4 s

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

  • 2,663 HTML elements

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

  • Improve image delivery

    150 ms · 246 KiB

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

  • 15 long tasks on the main thread

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

  • Reduce unused CSS

    150 ms · 50 KiB

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

  • Phones get a much slower page than desktops

    Desktop scores 63 but mobile only 15. A gap that wide usually means heavy scripts and images that hit phones hardest.

  • Legacy JavaScript

    7 KiB

    Polyfills for old browsers add 7 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.

1 checks passed
  • Server response: 72 ms

    72 ms

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

Core Web Vitals

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

  • Real-user CLS: 0.26

    0.26

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

  • Largest Contentful Paint: 11.6 s

    11.6 s

    Your largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “NEW: Custom Branded Pens. Put your brand in customers hands…”.

  • Time to Interactive: 19.6 s

    19.6 s

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

  • Cumulative Layout Shift: 0.896

    0.896

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

  • First Contentful Paint: 5.2 s

    5.2 s

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

  • Speed Index: 8.2 s

    8.2 s

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

  • Total Blocking Time: 770 ms

    770 ms

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

  • 13 images without width and height

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

  • Tap response (INP) held steady for real visitors

    0%

    Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 177 ms to 175 ms 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 INP: 141 ms

    141 ms

    Real visitors wait 141 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: 521 ms

    521 ms

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

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

    -21%

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

Images and page weight

1 to fix85
  • Page weight: 3.6 MB in 148 requests

    3.6 MB

    Your homepage downloads 3.6 MB in 148 requests on a phone: scripts 1.5 MB (25), images 1.3 MB (50) and fonts 673 KiB (9). Under 2 MB keeps phones on slow connections fast.

  • 9 images in older formats

    9 images (455 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.

  • 4 images below the first screen load straight away

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

  • About 1.0 g of CO₂ per visit

    1.03 g

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

1 checks passed
  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

7 to fixGoogle 7989
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

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

  • 2 tap targets too small

    2 tap targets are too small or too close together to hit reliably with a finger.

  • 2 images without alt text

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

  • 16 form fields without a label

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

  • 16 links without text

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

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

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

  • Headings skip levels

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

1 checks passed
  • 44 automated accessibility rules passed

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

SEO

3 to fixGoogle 7789
  • Title is long (83 characters)

    Your title is 83 characters, so Google will cut it off around 60: “instantprint - Online Printing Company UK, Printing Services Near Me | instantprint”.

  • 20 links crawlers can't follow

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

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

  • 334 internal links, 20 external

    The homepage links to 334 pages on instantprint.co.uk and 20 external pages.

7 checks passed
  • Meta description: 145 characters

    Your meta description is 145 characters: “We're the largest UK-based online printing company. We offer fast, high-quality, and affordable printing for business c…”.

  • One H1 headline

    Your main headline reads: “High Quality Online Printing Services”.

  • Canonical URL set

    The canonical URL is https://www.instantprint.co.uk/.

  • Structured data in place

    Structured data found: Organization.

  • 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.instantprint.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 contact details; description would complete it.

  • Text is in the HTML

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

  • llms.txt published

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

Other pages

100
  • 15 internal pages checked

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

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

  • 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

4 to fixGoogle 7774
  • 2 broken images

    2 images failed to load on a phone, for example https://bat.bing.com/action/0?ti=4018724&Ver=2&mid=d492eb4e-a259-4235-aa8b-9f0168902424&bo=3&sid=3f4f6090d30611f195a0db69d74a6961&vid=3f4f8d30d30611f1aa11ebea41208afd&vids=0&msclkid=N&pi=918639831&lg=.

  • 4 JavaScript errors while loading

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

  • Pasting is blocked

    A form field blocks pasting, which frustrates password managers and people on phones.

  • 2 distorted images

    2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

2 checks passed
  • Tap targets are thumb-sized

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

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix89
  • 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.

  • Thin social proof

    Social proof on the homepage: 6 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No form on the homepage

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

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

  • About 437 words of copy

    The homepage carries about 437 words of visible text.

7 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Request a free sample pack” and “Shop Now”.

  • 36 calls to action

    The homepage has 36 calls to action, for example “Shop All Products”, “Shop All Banners” and “Shop All Booklets”.

  • Analytics in place

    Analytics detected: Google Tag Manager and Google Analytics.

  • Direct contact links

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

  • Opening hours shown

    Your opening hours are on the homepage.

  • Phone number on the homepage

    Your phone number is on the homepage as a tap-to-call link.

  • 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

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, Microsoft Ads and Microsoft Clarity (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.

  • 14 cookies set on arrival

    14

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

  • 39 other companies contacted

    Loading the homepage contacts 39 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 instantprint.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

Framework
Tailwind CSS
Analytics
Google Analytics | Google Tag Manager
Hosting
AWS

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 instantprint.co.uk, including 19 speed issues, 3 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