Website review, no card needed
blossomandpear.com website review
Visit site (opens in a new tab)Reviewed 6 November 202638 issues · 91 checks
This review found 38 issues worth fixing on blossomandpear.com, 14 of them high impact, across 91 checks. The most urgent: improve image delivery. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
85B- #16,683 of 124,378 reviewed websitesbeats 82%
- #10,484 of 69,877 online storesbeats 80%
- #10,178 of 63,539 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.3 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.3 s |
| Jun 27, 2026 | 1.3 s |
| Jul 4, 2026 | 1.3 s |
| Jul 11, 2026 | 1.3 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.2 s |
| Aug 8, 2026 | 1.2 s |
| Aug 15, 2026 | 1.2 s |
| Aug 22, 2026 | 1.2 s |
| Aug 29, 2026 | 1.2 s |
| Sep 5, 2026 | 1.3 s |
| Sep 12, 2026 | 1.3 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.3 s |
| Oct 31, 2026 | 1.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 90 ms |
| May 23, 2026 | 92 ms |
| May 30, 2026 | 94 ms |
| Jun 6, 2026 | 92 ms |
| Jun 13, 2026 | 94 ms |
| Jun 20, 2026 | 95 ms |
| Jun 27, 2026 | 96 ms |
| Jul 4, 2026 | 96 ms |
| Jul 11, 2026 | 101 ms |
| Jul 18, 2026 | 104 ms |
| Jul 25, 2026 | 110 ms |
| Aug 1, 2026 | 113 ms |
| Aug 8, 2026 | 129 ms |
| Aug 15, 2026 | 133 ms |
| Aug 22, 2026 | 135 ms |
| Aug 29, 2026 | 137 ms |
| Sep 5, 2026 | 139 ms |
| Sep 12, 2026 | 145 ms |
| Sep 19, 2026 | 148 ms |
| Sep 26, 2026 | 153 ms |
| Oct 3, 2026 | 153 ms |
| Oct 10, 2026 | 153 ms |
| Oct 17, 2026 | 153 ms |
| Oct 24, 2026 | 149 ms |
| Oct 31, 2026 | 154 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
How it loaded on a phone
1.0 s
2.0 s
3.0 s
4.0 s
5.0 s
6.0 s
7.0 s
8.0 s
Speed
Improve image delivery
2.0 s · 2.3 MB30 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 2.0 s faster on a phone.
Render-blocking requests
1.0 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.
Main-thread work: 7.5 s
A phone's processor spends 7.5 s on main-thread work while loading, 2.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,537 HTML elements
The page has 4,537 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused JavaScript
2.1 MBAbout 2.1 MB of JavaScript is downloaded but never used on this page.
8 third-party services on the page
8 third-party services load with your homepage (route.com, Google Tag Manager and Shopify and others), adding 3.2 MB and 1.4 s of main-thread time.
Use efficient cache lifetimes
1.5 MB15 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
route.com adds 567 ms
567 msroute.com costs a phone 567 ms of main-thread work and 1.1 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.
Reduce unused CSS
450 ms · 196 KiBAbout 196 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Duplicated JavaScript
485 KiB485 KiB JavaScript is shipped twice across bundles.
Google Tag Manager adds 296 ms
296 msGoogle Tag Manager costs a phone 296 ms of main-thread work and 664 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.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 350 ms. During a long task the page ignores taps.
Shopify adds 181 ms
181 msShopify costs a phone 181 ms of main-thread work and 812 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.
Klaviyo adds 108 ms
108 msKlaviyo costs a phone 108 ms of main-thread work and 317 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
54 KiBPolyfills for old browsers add 54 KiB JavaScript that modern phones do not need.
Minify JavaScript
9 KiB9 KiB could be saved by minifying JavaScript.
Minify CSS
6 KiB6 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.
1 checks passed
Server response: 19 ms
19 msYour server sent the HTML in 19 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 45.7 s
45.7 sThe page becomes fully interactive after 45.7 s. Good is under 3.8 s.
Largest Contentful Paint: 7.4 s
7.4 sYour largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Wide banner of four children in matching red gingham Christ…”.
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 66% slower for real visitors
+66%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 90 ms to 154 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 595 ms
595 msScripts block taps and scrolling for 595 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
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.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 198 ms
198 msReal visitors wait 198 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 546 ms
546 msReal visitors wait 546 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.4 s
1.4 sThe first text or image appears after 1.4 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 23.9 MB in 654 requests
23.9 MBYour homepage downloads 23.9 MB in 654 requests on a phone: media 12.7 MB (1), images 5.4 MB (60) and scripts 3.5 MB (112). Under 2 MB keeps phones on slow connections fast.
1 image over 500 KB
8d3f993fd08e4756908c4f612954ee17.thumbnail.0000000000_1200x. weighs 531 KiB. On a phone connection a single image that size takes seconds.
An image on the first screen is lazy-loaded
the-little-harvest-edit-05.webp 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).
3 images in older formats
3 images (663 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 6.8 g of CO₂ per visit
6.76 gBy the Sustainable Web Design model, a visit to your homepage emits about 6.76 g of CO₂e: 811.6 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
11 tap targets too small
11 tap targets are too small or too close together to hit reliably with a finger.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
5 elements hidden from screen readers can still receive keyboard focus.
Elements must only use permitted ARIA attributes (1 element)
Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (31 elements)
All page content should be contained by landmarks: 31 elements on the page fail this check, rated moderate by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (7 elements).
1 checks passed
52 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 52 passed and 6 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
400 internal links, 5 external
The homepage links to 400 pages on blossomandpear.com and 5 external pages.
7 checks passed
Meta description: 142 characters
Your meta description is 142 characters: “Shop Beautiful Baby & Kids Clothing, Knitwear, Personalised Baby Gifts & Keepsakes At Blossom & Pear. Thoughtful Pieces…”.
One H1 headline
Your main headline reads: “Christmas 2026”.
Title: 63 characters
Your title is a healthy 63 characters: “Baby & Kids Clothing, Personalised Keepsakes – Blossom and Pear”.
Canonical URL set
The canonical URL is https://www.blossomandpear.com/.
Structured data in place
Structured data found: OnlineStore, Organization, Store 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://www.blossomandpear.com/sitemap.xml.
AI search readiness
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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (2,237 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.blossomandpear.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without an H1
https://www.blossomandpear.com/collections/christmas-collection and https://www.blossomandpear.com/collections 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 128 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.
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.
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
17 small tap targets
17 of 78 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 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.
About 1,184 words of copy
The homepage carries about 1,184 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: “SHOP NOW” and “SHOP CHRISTMAS”.
30 calls to action
The homepage has 30 calls to action, for example “Shop Now”, “Shop All Christmas” and “Shop All”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 103 testimonial or review blocks and 3 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Opening hours shown
Your opening hours are on the homepage.
LocalBusiness structured data
Your homepage describes the business with LocalBusiness JSON-LD, so search engines and AI assistants can read its address, hours and phone reliably.
Privacy and tracking
4 trackers load before any consent
4Before 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
9Opening 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.
35 other companies contacted
Loading the homepage contacts 35 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 blossomandpear.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 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · Pagefly Ai Page Builder · Klaviyo Email Marketing Sms · Gorgias Live Chat Helpdesk · Instafeed · Route Protection Tracking · Mandolly Product Customizer · Ecomsend Restock · Upcart · chimpstatic.com · kiwisizing.com · skynettechnologies.com · auspost-collect-app.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
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on blossomandpear.com, including 21 speed issues, 1 SEO issue 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.