Website review, no card needed
fedelicashmere.com website review
Visit site (opens in a new tab)Reviewed 21 October 202641 issues · 87 checks
This review found 41 issues worth fixing on fedelicashmere.com, 18 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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
71C- #97,609 of 120,920 reviewed websitesbeats 17%
- #60,018 of 68,447 online storesbeats 10%
- #55,782 of 62,371 Shopify storesbeats 9%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.9 s |
| May 9, 2026 | 3.0 s |
| May 16, 2026 | 3.0 s |
| May 23, 2026 | 2.9 s |
| May 30, 2026 | 2.9 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.9 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.9 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 3.0 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 151 ms |
| May 9, 2026 | 154 ms |
| May 16, 2026 | 150 ms |
| May 23, 2026 | 154 ms |
| May 30, 2026 | 151 ms |
| Jun 6, 2026 | 146 ms |
| Jun 13, 2026 | 146 ms |
| Jun 20, 2026 | 144 ms |
| Jun 27, 2026 | 146 ms |
| Jul 4, 2026 | 143 ms |
| Jul 11, 2026 | 140 ms |
| Jul 18, 2026 | 145 ms |
| Jul 25, 2026 | 145 ms |
| Aug 1, 2026 | 153 ms |
| Aug 8, 2026 | 159 ms |
| Aug 15, 2026 | 159 ms |
| Aug 22, 2026 | 160 ms |
| Aug 29, 2026 | 166 ms |
| Sep 5, 2026 | 167 ms |
| Sep 12, 2026 | 167 ms |
| Sep 19, 2026 | 166 ms |
| Sep 26, 2026 | 156 ms |
| Oct 3, 2026 | 154 ms |
| Oct 10, 2026 | 154 ms |
| Oct 17, 2026 | 160 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.5 s
0.9 s
1.4 s
1.8 s
2.3 s
2.8 s
3.2 s
3.7 s
Speed
Reduce unused JavaScript
3.3 s · 543 KiBAbout 543 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.3 s faster on a phone.
Render-blocking requests
1.1 s11 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Mobile performance score: 45
45/100Your mobile performance score is 45 (desktop: 70). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.4 s
A phone's processor spends 5.4 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,498 HTML elements
The page has 3,498 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 (Google Tag Manager, Klaviyo and Shopify and others), adding 11.6 MB and 1.1 s of main-thread time.
Shopify adds 125 ms
125 msShopify costs a phone 125 ms of main-thread work and 10.4 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.
Use efficient cache lifetimes
800 ms · 181 KiB44 files are served with short cache lifetimes, so returning visitors download them again (181 KiB).
Google Tag Manager adds 454 ms
454 msGoogle Tag Manager costs a phone 454 ms of main-thread work and 339 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
400 ms · 44 KiBPolyfills for old browsers add 44 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 400 ms faster on a phone.
Klaviyo adds 210 ms
210 msKlaviyo costs a phone 210 ms of main-thread work and 399 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 243 ms. During a long task the page ignores taps.
Improve image delivery
157 KiB1 image could be 157 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Duplicated JavaScript
100 ms · 18 KiB18 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 100 ms faster on a phone.
Reduce unused CSS
52 KiBAbout 52 KiB of CSS is downloaded but never applied on this page.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Phones get a much slower page than desktops
Desktop scores 70 but mobile only 45. A gap that wide usually means heavy scripts and images that hit phones hardest.
Minify JavaScript
8 KiB8 KiB could be saved by minifying JavaScript.
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: 65 ms
65 msYour server sent the HTML in 65 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 18.0 s
18.0 sYour largest element takes 18.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We use cookies to personalise content and ads, to provide s…”.
Time to Interactive: 19.1 s
19.1 sThe page becomes fully interactive after 19.1 s. Good is under 3.8 s.
Speed Index: 8.0 s
8.0 sVisually, the page fills in at 8.0 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Total Blocking Time: 633 ms
633 msScripts block taps and scrolling for 633 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 860 ms
860 msReal visitors wait 860 ms for your server to start answering (75th percentile). Good is under 800 ms.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 151 ms to 160 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.9 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 159 ms
159 msReal visitors wait 159 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.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 14.1 MB in 382 requests
14.1 MBYour homepage downloads 14.1 MB in 382 requests on a phone: media 10.2 MB (2), scripts 1.7 MB (141) and other files 1.3 MB (196). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
FEDELI_FW26_01191_360x.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).
1 image far larger than shown
125 KiB1 image is downloaded at several times the size a phone draws it, for example FEDELI_ICONICO_0288.jpg at 1,920 px wide, shown at 350 px. Resized copies would save about 125 KiB.
1 image below the first screen load straight away
1 image further down the page (178 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (50 KiB) is 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 4.0 g of CO₂ per visit
4.01 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.01 g of CO₂e: 480.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
12 images without alt text
12 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
17 links without text
17 visible links have no text or label, so screen readers cannot say where they go.
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.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Page is set to noindex
The robots meta tag says “noindex, nofollow”: Google is told not to list this page at all.
Blocked from indexing
Google's crawler is blocked from indexing this page.
Structured data has 1 problem
Structured data found (WebSite) but with 1 problem, for example “ld+json block 1 is not valid JSON (Unexpected token ']', ..."4\/", ] } " is not valid JSO)”.
149 internal links, 2 external
The homepage links to 149 pages on fedelicashmere.com and 2 external pages.
7 checks passed
Meta description: 159 characters
Your meta description is 159 characters: “We produce Knitwear & Swimwear that transcends time | Preserving traditions & forging new ones - Quality being …”.
One H1 headline
Your main headline reads: “The Geometry of Softness”.
Title: 59 characters
Your title is a healthy 59 characters: “Fedeli - Made in Italy | A History of Tradition in Knitwear”.
Canonical URL set
The canonical URL is https://www.fedelicashmere.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://www.fedelicashmere.com/sitemap.xml.
AI search readiness
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,001 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.fedelicashmere.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
15 linked pages hidden from search
https://www.fedelicashmere.com/en-usd/collections/man-all, https://www.fedelicashmere.com/en-usd/collections/mens-outerwear, https://www.fedelicashmere.com/en-usd/collections/mens-knitwear, https://www.fedelicashmere.com/en-usd/collections/mens-polos-and-t-shirts, https://www.fedelicashmere.com/en-usd/collections/mens-shirts and https://www.fedelicashmere.com/en-usd/collections/mens-pants and 9 others are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.
2 pages without an H1
https://www.fedelicashmere.com/en-usd/collections/mens-swim-trunks and https://www.fedelicashmere.com/en-usd/collections/summer-corner 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 60 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.
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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
2 checks passed
Tap targets are thumb-sized
40 of 44 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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: 28 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 467 words of copy
The homepage carries about 467 words of visible text.
3 checks passed
12 calls to action
The homepage has 12 calls to action, for example “Shop by Look”, “Contact Us” and “Get in touch”.
7 short forms
7 short forms (2 fields at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads 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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
21 other companies contacted
Loading the homepage contacts 21 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 fedelicashmere.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on fedelicashmere.com, including 21 speed issues, 3 SEO issues and 3 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.