Website review, no card needed
flowxjewelry.com website review
Visit site (opens in a new tab)Reviewed 8 November 202643 issues · 88 checks
This review found 43 issues worth fixing on flowxjewelry.com, 10 of them high impact, across 88 checks. The most urgent: page weight: 17.6 MB in 203 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
87B- #8,682 of 125,735 reviewed websitesbeats 90%
- #4,899 of 70,250 online storesbeats 90%
- #4,747 of 63,815 Shopify storesbeats 89%
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.4 s |
| Jun 6, 2026 | 1.3 s |
| Jun 13, 2026 | 1.3 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.4 s |
| Jul 18, 2026 | 1.3 s |
| Jul 25, 2026 | 1.3 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.4 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 2.0 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 112 ms |
| May 23, 2026 | 112 ms |
| May 30, 2026 | 115 ms |
| Jun 6, 2026 | 120 ms |
| Jun 13, 2026 | 121 ms |
| Jun 20, 2026 | 125 ms |
| Jun 27, 2026 | 127 ms |
| Jul 4, 2026 | 130 ms |
| Jul 11, 2026 | 130 ms |
| Jul 18, 2026 | 125 ms |
| Jul 25, 2026 | 121 ms |
| Aug 1, 2026 | 114 ms |
| Aug 8, 2026 | 120 ms |
| Aug 15, 2026 | 121 ms |
| Aug 22, 2026 | 119 ms |
| Aug 29, 2026 | 119 ms |
| Sep 5, 2026 | 106 ms |
| Sep 12, 2026 | 104 ms |
| Sep 19, 2026 | 107 ms |
| Sep 26, 2026 | 104 ms |
| Oct 3, 2026 | 103 ms |
| Oct 10, 2026 | 96 ms |
| Oct 17, 2026 | 91 ms |
| Oct 24, 2026 | 87 ms |
| Oct 31, 2026 | 89 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
Improve image delivery
3.8 MB22 images could be 3.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 79
79/100Your mobile performance score is 79. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
300 ms · 355 KiBAbout 355 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (upstackified.com, Shopify and Clarity and others), adding 593 KiB and 556 ms of main-thread time.
Render-blocking requests
600 ms8 files block the first paint until they finish downloading. Deferring or inlining them could save about 600 ms.
Main-thread work: 3.4 s
A phone's processor spends 3.4 s on main-thread work while loading, 1.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Use efficient cache lifetimes
304 KiB16 files are served with short cache lifetimes, so returning visitors download them again (304 KiB).
7 long tasks on the main thread
7 long tasks block the main thread while loading, the longest for 256 ms. During a long task the page ignores taps.
2,077 HTML elements
The page has 2,077 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
42 KiBAbout 42 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
30 KiBPolyfills for old browsers add 30 KiB JavaScript that modern phones do not need.
Duplicated JavaScript
23 KiB23 KiB JavaScript is shipped twice across bundles.
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: 21 ms
21 msYour server sent the HTML in 21 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 12.9 s
12.9 sThe page becomes fully interactive after 12.9 s. Good is under 3.8 s.
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 2.8 s
2.8 sYour largest element takes 2.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “JEWELRY BUILT FOR ATHLETES”. Most of its time is element render delay (2.6 s).
Total Blocking Time: 238 ms
238 msScripts block taps and scrolling for 238 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
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.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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: 2.1 s
2.1 sReal visitors wait 2.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 91 ms
91 msReal visitors wait 91 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 763 ms
763 msReal visitors wait 763 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 21% faster for real visitors
-21%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 112 ms to 89 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 17.6 MB in 203 requests
17.6 MBYour homepage downloads 17.6 MB in 203 requests on a phone: media 10.5 MB (1), images 5.2 MB (35) and scripts 941 KiB (58). Under 2 MB keeps phones on slow connections fast.
12 images far larger than shown
3.1 MB12 images are downloaded at several times the size a phone draws them, for example ryan_12.jpg at 1,856 px wide, shown at 147 px. Resized copies would save about 3.1 MB.
2 images over 500 KB
2 images weigh 1.1 MB together. On a phone connection a single image that size takes seconds.
5 images in older formats
5 images (1.0 MB) 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 5.0 g of CO₂ per visit
5.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.00 g of CO₂e: 599.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Invalid ARIA attributes
14 elements use ARIA attributes their role does not allow, which confuses screen readers.
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
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.
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (54 elements)
All page content should be contained by landmarks: 54 elements on the page fail this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails 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.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
23 links without text
23 visible links have no text or label, so screen readers cannot say where they go.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
ARIA role should be appropriate for the element (7 elements)
ARIA role should be appropriate for the element: 7 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h1 → h3 and h2 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 10 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 (68 characters)
Your title is 68 characters, so Google will cut it off around 60: “FlowX Jewelry | Number Necklaces and Waterproof Jewelry for Athletes”.
Meta description is long (183 characters)
Your meta description is 183 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 1 problem
Structured data found (Organization, WebPage and WebSite) but with 1 problem, for example “WebSite: potentialAction.target is not an absolute URL ("https://flowxjewelry.com/search?q={search_term_string}")”.
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.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
129 internal links, 0 external
The homepage links to 129 pages on flowxjewelry.com and 0 external pages.
5 checks passed
One H1 headline
Your main headline reads: “JEWELRY BUILT FOR ATHLETES”.
Canonical URL set
The canonical URL is https://flowxjewelry.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://flowxjewelry.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 (1,243 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://flowxjewelry.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://flowxjewelry.com/discount/DEALS declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://flowxjewelry.com/discount/DEALS all use the title “FlowX Jewelry | Number Necklaces and Waterproof Jewelry for Athletes”. Search engines can't tell which page to show for a search, so each competes with the others.
9 pages without a meta description
https://flowxjewelry.com/collections/pendants, https://flowxjewelry.com/collections/faith, https://flowxjewelry.com/collections/motivation-collection, https://flowxjewelry.com/collections/letters, https://flowxjewelry.com/collections/chains and https://flowxjewelry.com/collections/motocross and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.
11 pages without an H1
https://flowxjewelry.com/collections/pendants, https://flowxjewelry.com/collections/number-pendants, https://flowxjewelry.com/collections/faith, https://flowxjewelry.com/collections/sports-pendants, https://flowxjewelry.com/collections/motivation-collection and https://flowxjewelry.com/collections/letters and 5 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 56 found) and read each the way a search engine does.
3 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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
11 small tap targets
11 of 44 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: net::ERR_FAILED”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 698 words of copy
The homepage carries about 698 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP NOW” and “SHOP BY SPORT”.
9 calls to action
The homepage has 9 calls to action, for example “SHOP BEST SELLERS”, “SHOP NOW” and “Shop All →”.
8 short forms
8 short forms (1 field at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 75 testimonial or review blocks, a star rating and “OVER 100,000+ SATISFIED CUSTOMERS”.
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.
18 cookies set on arrival
18Opening the homepage sets 18 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.
28 other companies contacted
Loading the homepage contacts 28 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 flowxjewelry.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 9 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Intelligems A B Testing · Upstack Data Tracking Pixel · Platmart Color Swatches · Judge Me Reviews · Microsoft Clarity · Triplewhale · Omnisend · Fast Product Colors · Hitsy Progress Bar
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
- SvelteKit
- 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 43 issues on flowxjewelry.com, including 15 speed issues, 5 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.