Website review, no card needed
annsfabulousfinds.com website review
Visit site (opens in a new tab)Reviewed 8 November 202641 issues · 85 checks
This review found 41 issues worth fixing on annsfabulousfinds.com, 17 of them high impact, across 85 checks. The most urgent: render-blocking requests. 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
75C- #82,725 of 126,652 reviewed websitesbeats 30%
- #52,041 of 70,540 online storesbeats 22%
- #49,039 of 64,024 Shopify storesbeats 19%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.6 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.7 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.8 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.7 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.5 s |
| Sep 26, 2026 | 2.2 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.2 s |
| Oct 17, 2026 | 2.1 s |
| Oct 24, 2026 | 2.0 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 78 ms |
| May 23, 2026 | 77 ms |
| May 30, 2026 | 78 ms |
| Jun 6, 2026 | 78 ms |
| Jun 13, 2026 | 78 ms |
| Jun 20, 2026 | 79 ms |
| Jun 27, 2026 | 79 ms |
| Jul 4, 2026 | 79 ms |
| Jul 11, 2026 | 82 ms |
| Jul 18, 2026 | 86 ms |
| Jul 25, 2026 | 88 ms |
| Aug 1, 2026 | 94 ms |
| Aug 8, 2026 | 99 ms |
| Aug 15, 2026 | 106 ms |
| Aug 22, 2026 | 113 ms |
| Aug 29, 2026 | 106 ms |
| Sep 5, 2026 | 116 ms |
| Sep 12, 2026 | 112 ms |
| Sep 19, 2026 | 114 ms |
| Sep 26, 2026 | 114 ms |
| Oct 3, 2026 | 96 ms |
| Oct 10, 2026 | 96 ms |
| Oct 17, 2026 | 94 ms |
| Oct 24, 2026 | 90 ms |
| Oct 31, 2026 | 87 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
Render-blocking requests
3.0 s19 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.0 s.
Reduce unused JavaScript
1.3 s · 693 KiBAbout 693 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.3 s faster on a phone.
Signyfyd adds 1.4 s
1.4 sSignyfyd costs a phone 1.4 s of main-thread work and 282 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 29
29/100Your mobile performance score is 29. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.4 s
A phone's processor spends 6.4 s on main-thread work while loading, 3.7 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Signyfyd, Google Tag Manager and Klaviyo and others), adding 1.8 MB and 2.7 s of main-thread time.
Use efficient cache lifetimes
850 ms · 204 KiB16 files are served with short cache lifetimes, so returning visitors download them again (204 KiB).
Google Tag Manager adds 927 ms
927 msGoogle Tag Manager costs a phone 927 ms of main-thread work and 817 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.
Improve image delivery
800 ms · 164 KiB4 images could be 164 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 800 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 592 ms. During a long task the page ignores taps.
2,848 HTML elements
The page has 2,848 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
150 ms · 35 KiBAbout 35 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Minify CSS
90 ms · 5 KiB5 KiB could be saved by minifying CSS.
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need.
Minify JavaScript
6 KiB6 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.
1 checks passed
Server response: 11 ms
11 msYour server sent the HTML in 11 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.3 s
11.3 sYour largest element takes 11.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 21.8 s
21.8 sThe page becomes fully interactive after 21.8 s. Good is under 3.8 s.
Total Blocking Time: 1.2 s
1.2 sScripts block taps and scrolling for 1.2 s in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.7 s
3.7 sThe first text or image appears after 3.7 s on a phone. Good is under 1.8 s.
Speed Index: 6.5 s
6.5 sVisually, the page fills in at 6.5 s (Speed Index). Good is under 3.4 s.
48 images without width and height
48 images have no width and height attributes, so the layout jumps as each one loads.
Cumulative Layout Shift: 0.191
0.191The layout shifts by 0.191 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 78 ms to 87 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 16% slower for real visitors
+16%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 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.9 s
1.9 sReal visitors wait 1.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 97 ms
97 msReal visitors wait 97 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (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: 574 ms
574 msReal visitors wait 574 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 5.7 MB in 281 requests
5.7 MBYour homepage downloads 5.7 MB in 281 requests on a phone: images 2.7 MB (68), scripts 2.0 MB (90) and other files 713 KiB (99). Under 2 MB keeps phones on slow connections fast.
13 images below the first screen load straight away
13 images further down the page (423 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
99 KiB1 image is downloaded at several times the size a phone draws it, for example slide_4.jpg at 1,887 px wide, shown at 390 px. Resized copies would save about 99 KiB.
1 image in older formats
1 image (54 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 1.6 g of CO₂ per visit
1.60 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.60 g of CO₂e: 192.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
39 images without alt text
39 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (70 elements)
All page content should be contained by landmarks: 70 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
41 form fields without a label
41 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 link without text
1 visible link has no text or label, so screen readers cannot say where it goes.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
1 checks passed
36 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 36 passed and 7 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “AFF Luxury Consignment | Buy & Sell Authentic Designer Luxury Items”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
44 H1 headlines
There are 44 <h1> headlines (“Sale | November Edit”, “.shappify-sales-icon-product{ } Hermès La Nouvell…” and “.shappify-sales-icon-product{ } Chanel Old Medium…”). One clear main headline is easier for people and search engines.
Open Graph partly set
Open Graph is missing og:title and og:description, so shared links fall back to guesses.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
719 internal links, 5 external
The homepage links to 719 pages on annsfabulousfinds.com and 5 external pages.
4 checks passed
Meta description: 156 characters
Your meta description is 156 characters: “Ann's Fabulous Finds is the best source for authentic pre-owned designer handbags and jewelry. Buy, sell, & consign aut…”.
Canonical URL set
The canonical URL is https://www.annsfabulousfinds.com/.
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.annsfabulousfinds.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.
No llms.txt
There is no https://www.annsfabulousfinds.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
2 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 (2,010 words), so crawlers that don't run JavaScript still read it.
Other pages
5 pages without a meta description
https://www.annsfabulousfinds.com/collections/new-arrivals, https://www.annsfabulousfinds.com/collections/chanel-on-sale, https://www.annsfabulousfinds.com/collections/chanel-handbags, https://www.annsfabulousfinds.com/collections/chanel-jewelry and https://www.annsfabulousfinds.com/collections/chanel-accessories 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 112 found) and read each the way a search engine does.
6 checks passed
Linked pages load
10 pages of 15 loaded without an error (the rest turned automated requests away).
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 10 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://bat.bing.com/action/0?ti=187060413&tm=shpfy_ui&Ver=2&mid=64bbc7cd-f2db-4943-b073-771c91df8777&bo=1&sid=f09951d0db4611f1b7b0dd9bfdf5a7ad&vid=f0993fc0db4611f1b57ba1b83da923b1&vids=1&msclkid=N&pi.
29 small tap targets
29 of 47 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 JavaScript errors while loading
3 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 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.
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 438 words of copy
The homepage carries about 438 words of visible text.
4 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact Us”, “Dior Medium Gray Oblique Book Tote” and “Register”.
41 short forms
41 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: a star rating and 38 trust badges.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Ads (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.
17 cookies set on arrival
17Opening the homepage sets 17 cookies, 2 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.
33 other companies contacted
Loading the homepage contacts 33 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 annsfabulousfinds.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 annsfabulousfinds.com, including 18 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.