Website review, no card needed
simoneandivy.com website review
Visit site (opens in a new tab)Reviewed 10 November 202640 issues · 87 checks
This review found 40 issues worth fixing on simoneandivy.com, 16 of them high impact, across 87 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
68D- #101,386 of 115,081 reviewed websitesbeats 10%
- #61,930 of 66,376 online storesbeats 5%
- #57,277 of 60,708 Shopify storesbeats 5%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.6 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.8 s |
| Oct 10, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 146 ms |
| May 30, 2026 | 161 ms |
| Jun 6, 2026 | 168 ms |
| Jun 13, 2026 | 119 ms |
| Jul 18, 2026 | 153 ms |
| Aug 1, 2026 | 146 ms |
| Aug 8, 2026 | 146 ms |
| Aug 15, 2026 | 138 ms |
| Aug 29, 2026 | 128 ms |
| Sep 5, 2026 | 133 ms |
| Sep 12, 2026 | 153 ms |
| Sep 19, 2026 | 160 ms |
| Sep 26, 2026 | 166 ms |
| Oct 3, 2026 | 196 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.1 s
3.1 s
4.1 s
5.1 s
6.2 s
7.2 s
8.2 s
Speed
Improve image delivery
5.3 s · 966 KiB16 images could be 966 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 5.3 s faster on a phone.
Reduce unused JavaScript
4.8 s · 916 KiBAbout 916 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.8 s faster on a phone.
Render-blocking requests
1.6 s4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Reduce unused CSS
1.1 s · 126 KiBAbout 126 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Main-thread work: 7.1 s
A phone's processor spends 7.1 s on main-thread work while loading, 3.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4,054 HTML elements
The page has 4,054 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Google Tag Manager and rebuyengine.com and others), adding 2.7 MB and 1.5 s of main-thread time.
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
550 ms · 131 KiB12 files are served with short cache lifetimes, so returning visitors download them again (131 KiB).
Legacy JavaScript
550 ms · 82 KiBPolyfills for old browsers add 82 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 550 ms faster on a phone.
Shopify adds 515 ms
515 msShopify costs a phone 515 ms of main-thread work and 997 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.
Google Tag Manager adds 407 ms
407 msGoogle Tag Manager costs a phone 407 ms of main-thread work and 508 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 158 ms
158 msrebuyengine.com costs a phone 158 ms of main-thread work and 702 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.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 184 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 3 KiB3 KiB could be saved by minifying JavaScript.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
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: 25 ms
25 msYour server sent the HTML in 25 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 38.1 s
38.1 sYour largest element takes 38.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Slideshow Image 2”.
Time to Interactive: 38.3 s
38.3 sThe page becomes fully interactive after 38.3 s. Good is under 3.8 s.
Speed Index: 11.5 s
11.5 sVisually, the page fills in at 11.5 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 624 ms
624 msScripts block taps and scrolling for 624 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.
Tap response (INP) got 18% slower for real visitors
+18%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 146 ms to 196 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
2 checks passed
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.035
0.035The layout barely moves while loading (CLS 0.035, good is under 0.1).
Images and page weight
Page weight: 6.7 MB in 430 requests
6.7 MBYour homepage downloads 6.7 MB in 430 requests on a phone: scripts 2.6 MB (193), images 2.2 MB (30) and other files 1.0 MB (153). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
image-44.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).
About 1.9 g of CO₂ per visit
1.91 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.91 g of CO₂e: 229.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Invalid ARIA attributes
2 elements use ARIA attributes their role does not allow, which confuses screen readers.
Certain ARIA roles must contain particular children (2 elements)
Certain ARIA roles must contain particular children: 2 elements on the page fail this check, rated critical by axe-core.
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
10 tap targets too small
10 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor 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. (2 elements).
2 checks passed
Every image has alt text
All 79 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 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
Title is long (69 characters)
Your title is 69 characters, so Google will cut it off around 60: “Home Decor, Home Goods and Furniture | Simone & Ivy | Alberta, Canada”.
8 H1 headlines
There are 8 <h1> headlines (“THE MAGIC IS IN THE MAKING”, “HOLIDAY BUNDLES” and “GIFTS FOR EVERYONE”). One clear main headline is easier for people and search engines.
Meta description is long (174 characters)
Your meta description is 174 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (FurnitureStore, Organization and WebSite) but with 1 problem, for example “Organization: url points at a different host (https://simoneandivy.ca)”.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
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.
423 internal links, 118 external
The homepage links to 423 pages on simoneandivy.com and 118 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://simoneandivy.com/.
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://simoneandivy.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: 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,261 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://simoneandivy.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
4 pages without a meta description
https://simoneandivy.com/pages/custom-consults, https://simoneandivy.com/pages/window-coverings, https://simoneandivy.com/blogs/recipes and https://simoneandivy.com/pages/partner-program have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages without an H1
https://simoneandivy.com/pages/window-coverings, https://simoneandivy.com/blogs/holiday, https://simoneandivy.com/blogs/transform-your-space, https://simoneandivy.com/blogs/design-tips-be-inspired, https://simoneandivy.com/blogs/projects and https://simoneandivy.com/blogs/recipes and 2 others 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 172 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.
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
10 broken images
10 images failed to load on a phone, for example https://scontent.xx.fbcdn.net/v/t51.2885-15/488878158_1033306262240956_9057507043684007530_n.jpg?_nc_cat=101&ccb=1-7&_nc_sid=7d201b&_nc_ohc=P2sh01y-QNkQ7kNvwHdP9t6&_nc_oc=AdlZaq2FNpl04R2rMAUJNDL9ugIR_.
16 small tap targets
16 of 74 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 “Failed to load resource: the server responded with a status of 403 ()”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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,135 words of copy
The homepage carries about 1,135 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 HOLIDAY” and “SHOP THE SALE”.
49 calls to action
The homepage has 49 calls to action, for example “Contact”, “Shop All Holiday” and “Shop All Tree Accessories”.
26 short forms
26 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 20 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Opening hours shown
Your opening hours are on the homepage.
Phone number on the homepage
Your phone number is on the homepage.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 3 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.
23 cookies set on arrival
23Opening the homepage sets 23 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.
50 other companies contacted
Loading the homepage contacts 50 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 simoneandivy.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Inbox · Klaviyo Email Marketing Sms · Rebuy Personalization Engine · Judge Me Reviews · Kaching Bundles · File Uploads By Uploadkit · Recurpaydevelopment · Bestpush · hextom.com · rebuyengine.com · cloudfront.net
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
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on simoneandivy.com, including 18 speed issues, 6 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.