Website review, no card needed
fionafranchimon.com website review
Visit site (opens in a new tab)Reviewed 7 November 202630 issues · 81 checks
This review found 30 issues worth fixing on fionafranchimon.com, 9 of them high impact, across 81 checks. The most urgent: avoid multiple page redirects. 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
87B- #8,335 of 121,058 reviewed websitesbeats 90%
- #4,816 of 68,509 online storesbeats 89%
- #4,665 of 62,430 Shopify storesbeats 89%
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.4 s |
| Jun 6, 2026 | 1.4 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.4 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.4 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.4 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.4 s |
| Sep 26, 2026 | 1.3 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.3 s |
| Oct 17, 2026 | 1.2 s |
| Oct 24, 2026 | 1.2 s |
| Oct 31, 2026 | 1.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 113 ms |
| May 23, 2026 | 113 ms |
| May 30, 2026 | 113 ms |
| Jun 6, 2026 | 112 ms |
| Jun 13, 2026 | 115 ms |
| Jun 20, 2026 | 118 ms |
| Jun 27, 2026 | 118 ms |
| Jul 4, 2026 | 120 ms |
| Jul 11, 2026 | 120 ms |
| Jul 18, 2026 | 119 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 124 ms |
| Aug 8, 2026 | 129 ms |
| Aug 15, 2026 | 132 ms |
| Aug 22, 2026 | 136 ms |
| Aug 29, 2026 | 132 ms |
| Sep 5, 2026 | 130 ms |
| Sep 12, 2026 | 127 ms |
| Sep 19, 2026 | 128 ms |
| Sep 26, 2026 | 128 ms |
| Oct 3, 2026 | 128 ms |
| Oct 10, 2026 | 129 ms |
| Oct 17, 2026 | 128 ms |
| Oct 24, 2026 | 128 ms |
| Oct 31, 2026 | 128 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
0.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Avoid multiple page redirects
4.4 sThe page goes through 3 redirects before it starts loading, costing about 4.4 s. Link and advertise the final URL directly.
Render-blocking requests
1.1 s14 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
8 third-party services on the page
8 third-party services load with your homepage (negate.io, Shopify and fionafranchimon.us and others), adding 2.6 MB and 846 ms of main-thread time.
Mobile performance score: 65
65/100Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.
Document request latency
450 msThe HTML itself could arrive about 450 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce unused JavaScript
448 KiBAbout 448 KiB of JavaScript is downloaded but never used on this page.
fionafranchimon.us adds 181 ms
181 msfionafranchimon.us costs a phone 181 ms of main-thread work and 1.7 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.
Shopify adds 251 ms
251 msShopify costs a phone 251 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.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
negate.io adds 257 ms
257 msnegate.io costs a phone 257 ms of main-thread work and 41 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.
2,342 HTML elements
The page has 2,342 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Use efficient cache lifetimes
150 ms · 90 KiB7 files are served with short cache lifetimes, so returning visitors download them again (90 KiB).
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 102 ms. During a long task the page ignores taps.
Improve image delivery
27 KiB1 image could be 27 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused CSS
21 KiBAbout 21 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 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.
Duplicated JavaScript
5 KiB5 KiB JavaScript is shipped twice across bundles.
Minify CSS
2 KiB2 KiB could be saved by minifying CSS.
1 checks passed
Server response: 8 ms
8 msYour server sent the HTML in 8 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.7 s
9.7 sYour largest element takes 9.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 12.6 s
12.6 sThe page becomes fully interactive after 12.6 s. Good is under 3.8 s.
First Contentful Paint: 4.0 s
4.0 sThe first text or image appears after 4.0 s on a phone. Good is under 1.8 s.
Speed Index: 4.0 s
4.0 sVisually, the page fills in at 4.0 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 113 ms to 128 ms 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.1 s
1.1 sReal visitors wait 1.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 88 ms
88 msReal visitors wait 88 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: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 579 ms
579 msReal visitors wait 579 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 96 ms
96 msScripts block the page for only 96 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 3.4 MB in 394 requests
3.4 MBYour homepage downloads 3.4 MB in 394 requests on a phone: scripts 1.2 MB (118), other files 1.0 MB (145) and images 697 KiB (42). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
VOGUE_LIVING_PRODUCT.png 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
12 KiB1 image is downloaded at several times the size a phone draws it, for example 4c79ee0393b14d3c87c153c639fe9386.thumbnail.0000000000.jpg at 533 px wide, shown at 158 px. Resized copies would save about 12 KiB.
About 1.0 g of CO₂ per visit
0.96 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.96 g of CO₂e: 115.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 use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
1 checks passed
52 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: 52 passed and 2 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
One H1 headline
Your <h1> is empty.
285 internal links, 9 external
The homepage links to 285 pages on fionafranchimon.com and 9 external pages.
7 checks passed
Meta description: 145 characters
Your meta description is 145 characters: “The Nº1 Hairpin: 5x stronger grip, zero damage, all-day volume. Create endless hairstyles | The high-performance Hairca…”.
Title: 42 characters
Your title is a healthy 42 characters: “Fiona Franchimon | Haircare | No 1 Hairpin”.
Canonical URL set
The canonical URL is https://www.fionafranchimon.com/en-us.
Structured data in place
Structured data found: Organization and WebSite.
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.fionafranchimon.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 (3,200 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.fionafranchimon.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
5 pages without a meta description
https://www.fionafranchimon.com/en-us/collections/all, https://www.fionafranchimon.com/en-us/collections/no1-hairpin, https://www.fionafranchimon.com/en-us/policies/shipping-policy, https://www.fionafranchimon.com/en-us/collections/all-holiday-deals and https://www.fionafranchimon.com/en-us/collections/treatment-oil-serum have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.fionafranchimon.com/en-us/products/n%C2%BA1-hairpin-custom-collection-set-6-pcs, whose canonical is https://www.fionafranchimon.com/en-us/products/n%c2%ba1-hairpin-custom-collection-set-6-pcs. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
8 pages without an H1
https://www.fionafranchimon.com/en-us/collections/all, https://www.fionafranchimon.com/en-us/collections/no1-hairpin, https://www.fionafranchimon.com/en-us/policies/shipping-policy, https://www.fionafranchimon.com/en-us/collections/all-holiday-deals, https://www.fionafranchimon.com/en-us/products/n%C2%BA1-hairpin-custom-collection-set-6-pcs and https://www.fionafranchimon.com/en-us/pages/statement-import-tariffs 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 131 found) and read each the way a search engine does.
4 checks passed
Linked pages load
8 pages of 15 loaded without an error (the rest turned automated requests away).
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 8 pages that loaded have a <title>.
Best practices
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 429 ()”.
2 checks passed
Tap targets are thumb-sized
38 of 38 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 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 691 words of copy
The homepage carries about 691 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW”.
9 calls to action
The homepage has 9 calls to action, for example “Shop all”, “Learn more” and “SHOP NOW”.
16 short forms
16 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
10 cookies set on arrival
10Opening the homepage sets 10 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.
26 other companies contacted
Loading the homepage contacts 26 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 fionafranchimon.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 10 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Geolocation Flow · Xapps Geo · Forms · Pushowl · Product Colors · Freegifts · chimpstatic.com · cloudfront.net · bogos.io · amazonaws.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
- 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 30 issues on fionafranchimon.com, including 16 speed issues, 2 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.