Website review, no card needed

perkyblenders.com logo

perkyblenders.com website review

Visit site (opens in a new tab)Reviewed 5 November 202628 issues · 81 checks

This review found 28 issues worth fixing on perkyblenders.com, 8 of them high impact, across 81 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 s926 msMay 16Oct 311.1 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.2 s
May 23, 20261.1 s
May 30, 20261.0 s
Jun 6, 2026971 ms
Jun 13, 2026970 ms
Jun 20, 20261.2 s
Jun 27, 20261.2 s
Jul 4, 20261.2 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.1 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.3 s
Aug 29, 20261.2 s
Sep 5, 20261.1 s
Sep 12, 20261.0 s
Sep 19, 2026986 ms
Sep 26, 2026991 ms
Oct 3, 20261.1 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Real-visitor tap response (INP)75th percentile, phones
123 ms77 msMay 16Oct 3183 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026107 ms
May 23, 2026112 ms
May 30, 2026118 ms
Jun 6, 2026116 ms
Jun 13, 2026113 ms
Jun 20, 2026106 ms
Jun 27, 2026105 ms
Jul 4, 2026104 ms
Jul 11, 2026103 ms
Jul 18, 2026104 ms
Jul 25, 2026102 ms
Aug 1, 2026104 ms
Aug 8, 2026104 ms
Aug 15, 2026105 ms
Aug 22, 2026104 ms
Aug 29, 202694 ms
Sep 5, 202691 ms
Sep 12, 202689 ms
Sep 19, 202690 ms
Sep 26, 202693 ms
Oct 3, 202688 ms
Oct 10, 202688 ms
Oct 17, 202685 ms
Oct 24, 202682 ms
Oct 31, 202683 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 perkyblenders.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. perkyblenders.com at 0.7 s0.7 s
  2. perkyblenders.com at 1.4 s1.4 s
  3. perkyblenders.com at 2.2 s2.2 s
  4. perkyblenders.com at 2.9 s2.9 s
  5. perkyblenders.com at 3.6 s3.6 s
  6. perkyblenders.com at 4.3 s4.3 s
  7. perkyblenders.com at 5.1 s5.1 s
  8. perkyblenders.com at 5.8 s5.8 s

Speed

6 to fix65
  • Reduce unused JavaScript

    2.4 s · 453 KiB

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

  • Mobile performance score: 65

    65/100

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

  • 7 third-party services on the page

    7 third-party services load with your homepage (Shopify, rechargecdn.com and Klaviyo and others), adding 904 KiB and 816 ms of main-thread time.

  • Shopify adds 545 ms

    545 ms

    Shopify costs a phone 545 ms of main-thread work and 464 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.2 s

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

  • rechargecdn.com adds 154 ms

    154 ms

    rechargecdn.com costs a phone 154 ms of main-thread work and 297 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.

  • Improve image delivery

    150 ms · 194 KiB

    4 images could be 194 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.

  • Reduce unused CSS

    180 ms · 39 KiB

    About 39 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 180 ms faster on a phone.

  • Render-blocking requests

    200 ms

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

  • 4 long tasks on the main thread

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

  • Use efficient cache lifetimes

    100 ms · 22 KiB

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

  • Legacy JavaScript

    25 KiB

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

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

    7 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 10.6 s

    10.6 s

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

  • Time to Interactive: 10.6 s

    10.6 s

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

  • Speed Index: 6.4 s

    6.4 s

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

  • First Contentful Paint: 2.6 s

    2.6 s

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

  • Largest content (LCP) held steady for real visitors

    -2%

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

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

    1.2 s

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

  • Real-user INP: 97 ms

    97 ms

    Real visitors wait 97 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.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: 585 ms

    585 ms

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

  • Tap response (INP) got 25% faster for real visitors

    -25%

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

  • Total Blocking Time: 105 ms

    105 ms

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

  • Cumulative Layout Shift: 0

    0

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

Images and page weight

1 to fix85
  • Page weight: 2.5 MB in 240 requests

    2.5 MB

    Your homepage downloads 2.5 MB in 240 requests on a phone: scripts 1.1 MB (123), other files 757 KiB (98) and images 419 KiB (6). Under 2 MB keeps phones on slow connections fast.

  • 3 images in older formats

    3 images (157 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.

  • About 0.7 g of CO₂ per visit

    0.70 g

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

2 checks passed
  • Images load when needed

    Images below the first screen wait until the visitor scrolls to them.

  • Images are sized for phones

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

Accessibility

5 to fixGoogle 9394
  • 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.

  • ARIA dialog and alertdialog nodes should have an accessible name (1 element)

    ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

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

  • 11 links without text

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

  • Hidden but focusable

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

2 checks passed
  • Every image has alt text

    All 36 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

3 to fixGoogle 10082
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Meta description is short (56 characters)

    Your meta description is only 56 characters: “Roasted in East London. Posted Everywhere. For Everyone.”. 70 to 160 characters is enough to sell the click.

  • No social preview image

    No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

  • 126 internal links, 7 external

    The homepage links to 126 pages on perkyblenders.com and 7 external pages.

5 checks passed
  • Title: 31 characters

    Your title is a healthy 31 characters: “Perky Blenders Specialty Coffee”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: Organization.

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

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://perkyblenders.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.

2 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 (480 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 2 pages without an H1

    https://perkyblenders.com/collections/subscriptions and https://perkyblenders.com/collections/gift-subscriptions 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 58 found) and read each the way a search engine does.

6 checks passed
  • Linked pages load

    5 pages of 15 loaded without an error (the rest turned automated requests away).

  • Canonical URLs point to themselves

    No page we checked hands its ranking to a different URL.

  • Every page has a meta description

    All 5 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 5 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    19 of 20 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

6 to fix61
  • No social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

  • Only about 196 words

    The homepage has only about 196 words of visible text; thin pages give Google and first-time buyers little to go on.

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

3 checks passed
  • Clear next step on the first screen

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

  • 7 calls to action

    The homepage has 7 calls to action, for example “CONTACT US”, “SHOP COTM” and “SHOP HALF CAFF”.

  • 9 short forms

    9 short forms (1 field at most) are right on the homepage, asking for an email.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 9 cookies set on arrival

    9

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

  • 22 other companies contacted

    Loading the homepage contacts 22 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 perkyblenders.com, 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 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Klaviyo Email Marketing Sms · Vo Product Options · Forms · rechargecdn.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
Bootstrap
E-commerce
Shopify
Hosting
Shopify

Company

Headquarters
London

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 28 issues on perkyblenders.com, including 10 speed issues, 3 SEO issues and 6 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