Website review, no card needed

jonnyssister.com logo

jonnyssister.com website review

Visit site (opens in a new tab)Reviewed 13 November 202634 issues · 84 checks

This review found 34 issues worth fixing on jonnyssister.com, 12 of them high impact, across 84 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
2.4 s1.2 sMay 23Nov 71.7 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20262.2 s
May 30, 20262.3 s
Jun 6, 20262.3 s
Jun 13, 20262.2 s
Jun 20, 20262.0 s
Jun 27, 20261.9 s
Jul 4, 20261.7 s
Jul 11, 20261.8 s
Jul 18, 20261.9 s
Jul 25, 20261.9 s
Aug 1, 20261.9 s
Aug 8, 20261.8 s
Aug 15, 20261.9 s
Aug 22, 20261.7 s
Aug 29, 20261.6 s
Sep 5, 20261.7 s
Sep 12, 20261.6 s
Sep 19, 20261.6 s
Sep 26, 20261.7 s
Oct 3, 20261.3 s
Oct 10, 20261.3 s
Oct 17, 20261.5 s
Oct 24, 20261.6 s
Oct 31, 20261.7 s
Nov 7, 20261.7 s
Real-visitor tap response (INP)75th percentile, phones
179 ms111 msMay 23Nov 7155 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026171 ms
May 30, 2026164 ms
Jun 6, 2026159 ms
Jun 13, 2026161 ms
Jun 20, 2026162 ms
Jun 27, 2026149 ms
Jul 4, 2026149 ms
Jul 11, 2026144 ms
Jul 18, 2026137 ms
Jul 25, 2026146 ms
Aug 1, 2026133 ms
Aug 8, 2026136 ms
Aug 15, 2026139 ms
Aug 22, 2026136 ms
Aug 29, 2026133 ms
Sep 5, 2026136 ms
Sep 12, 2026134 ms
Sep 19, 2026128 ms
Sep 26, 2026136 ms
Oct 3, 2026124 ms
Oct 10, 2026119 ms
Oct 17, 2026129 ms
Oct 24, 2026132 ms
Oct 31, 2026144 ms
Nov 7, 2026155 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 jonnyssister.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. jonnyssister.com at 0.4 s0.4 s
  2. jonnyssister.com at 0.8 s0.8 s
  3. jonnyssister.com at 1.1 s1.1 s
  4. jonnyssister.com at 1.5 s1.5 s
  5. jonnyssister.com at 1.9 s1.9 s
  6. jonnyssister.com at 2.3 s2.3 s
  7. jonnyssister.com at 2.6 s2.6 s
  8. jonnyssister.com at 3.0 s3.0 s

Speed

10 to fix58
  • Reduce unused JavaScript

    3.2 s · 583 KiB

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

  • Use efficient cache lifetimes

    1.7 s · 420 KiB

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

  • Render-blocking requests

    1.6 s

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

  • 3,527 HTML elements

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

  • Improve image delivery

    100 ms · 2.3 MB

    60 images could be 2.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

  • Mobile performance score: 58

    58/100

    Your mobile performance score is 58. 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 (Shopify, rebuyengine.com and Clarity and others), adding 1.6 MB and 648 ms of main-thread time.

  • Main-thread work: 3.5 s

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

  • Shopify adds 155 ms

    155 ms

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

  • rebuyengine.com adds 119 ms

    119 ms

    rebuyengine.com costs a phone 119 ms of main-thread work and 649 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.

  • Legacy JavaScript

    150 ms · 29 KiB

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

  • Reduce unused CSS

    130 ms · 43 KiB

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

  • 7 long tasks on the main thread

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

  • Duplicated JavaScript

    50 ms · 32 KiB

    32 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 50 ms faster on a phone.

  • Font display

    50 ms

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

  • Minify CSS

    6 KiB

    6 KiB could be saved by minifying CSS.

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

    51 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 27.6 s

    27.6 s

    Your largest element takes 27.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “650+ Gifts!”.

  • Time to Interactive: 28.4 s

    28.4 s

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

  • First Contentful Paint: 4.3 s

    4.3 s

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

  • Speed Index: 8.0 s

    8.0 s

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

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

    158 ms

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

  • Real-user CLS: 0.01

    0.01

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

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

    367 ms

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

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

    -11%

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

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

    -24%

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

  • Total Blocking Time: 122 ms

    122 ms

    Scripts block the page for only 122 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

3 to fix53
  • Page weight: 7.7 MB in 380 requests

    7.7 MB

    Your homepage downloads 7.7 MB in 380 requests on a phone: images 3.1 MB (69), other files 2.3 MB (154) and scripts 1.7 MB (131). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    pink-ribbons-festive-new-year-party-background-with-design-s 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

    6 KiB

    1 image is downloaded at several times the size a phone draws it, for example 1603733114-37270000_1296x_101a9270-f40c-4ee5-9f9d-6df972dfab at 400 px wide, shown at 126 px. Resized copies would save about 6 KiB.

  • 10 images in older formats

    10 images (439 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 2.2 g of CO₂ per visit

    2.19 g

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

Accessibility

7 to fixGoogle 7993
  • Invalid ARIA attributes

    1 element use ARIA attributes their role does not allow, which confuses screen readers.

  • 42 text elements with low contrast

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

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

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

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 15 links without text

    15 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 (19 elements)

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

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

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

2 checks passed
  • Every image has alt text

    All 89 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 59 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 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

3 to fixGoogle 9285
  • Title is short (14 characters)

    Your title is only 14 characters: “Jonny's Sister”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • Meta description is long (269 characters)

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

  • No social preview image

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

  • 316 internal links, 7 external

    The homepage links to 316 pages on jonnyssister.com and 7 external pages.

5 checks passed
  • One H1 headline

    Your main headline reads: “Jonny's Sister”.

  • Canonical URL set

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

  • Structured data in place

    Structured data found: BreadcrumbList and WebSite.

  • 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://jonnyssister.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,760 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://jonnyssister.com/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://jonnyssister.com/collections/tilly-pig, https://jonnyssister.com/collections/personalised-childrens-animal-sweatshirts, https://jonnyssister.com/collections/wedding-1, https://jonnyssister.com/collections/gardener, https://jonnyssister.com/collections/frequent-traveller-1 and https://jonnyssister.com/collections/drinks-connoisseur-1 and 9 others 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 89 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
  • 26 small tap targets

    26 of 85 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 4 JavaScript errors while loading

    4 errors were logged to the browser console while the page loaded, for example “Wingify is not defined”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

2 to fix75
  • No call to action on the first screen

    On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

  • Thin social proof

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

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

    The homepage carries about 899 words of visible text.

4 checks passed
  • 4 calls to action

    The homepage has 4 calls to action, for example “Shop our products”, “Shop Now” and “Subscribe”.

  • 4 short forms

    4 short forms (2 fields at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager and Microsoft Clarity.

  • Direct contact links

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

Privacy and tracking

1 to fix
  • 7 trackers load before any consent

    7

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 2 mores (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.

  • 28 cookies set on arrival

    28

    Opening the homepage sets 28 cookies, 1 of them by other companies (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.

  • 52 other companies contacted

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

Apps your storefront loads

Zepto Product Personalizer · Wingify · Rebuy Personalization Engine · Instant Ai Page Builder · Multifeeds · Klaviyo Email Marketing Sms · Gorgias Live Chat Helpdesk · Firework Shoppable Video Ugc · Linkedoption · Yotpo Product Reviews · Thoughtmetric · Omnisend · Product Labels And Badges · cloudfront.net · orderdeadline.com · rebuyengine.com · trustpilot.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
Analytics
Google Tag Manager | Microsoft Clarity
Hosting
Shopify

Company

Headquarters
Yeovil

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

Go beyond the website

What your $25 Growth Playbook adds

This review found 34 issues on jonnyssister.com, including 14 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