Website review, no card needed
julievos.com website review
Visit site (opens in a new tab)Reviewed 4 November 202635 issues · 87 checks
This review found 35 issues worth fixing on julievos.com, 13 of them high impact, across 87 checks. The most urgent: page weight: 51.2 MB in 437 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
78C- #59,031 of 116,487 reviewed websitesbeats 44%
- #39,079 of 66,776 online storesbeats 36%
- #37,377 of 60,929 Shopify storesbeats 33%
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.7 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.7 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 170 ms |
| May 23, 2026 | 172 ms |
| May 30, 2026 | 179 ms |
| Jun 6, 2026 | 203 ms |
| Jun 13, 2026 | 213 ms |
| Jun 20, 2026 | 216 ms |
| Jun 27, 2026 | 220 ms |
| Jul 4, 2026 | 220 ms |
| Jul 11, 2026 | 212 ms |
| Jul 18, 2026 | 204 ms |
| Jul 25, 2026 | 195 ms |
| Aug 1, 2026 | 191 ms |
| Aug 8, 2026 | 186 ms |
| Aug 15, 2026 | 182 ms |
| Aug 22, 2026 | 180 ms |
| Aug 29, 2026 | 180 ms |
| Sep 5, 2026 | 180 ms |
| Sep 12, 2026 | 186 ms |
| Sep 19, 2026 | 187 ms |
| Sep 26, 2026 | 190 ms |
| Oct 3, 2026 | 194 ms |
| Oct 10, 2026 | 188 ms |
| Oct 17, 2026 | 188 ms |
| Oct 24, 2026 | 187 ms |
| Oct 31, 2026 | 184 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.9 s
1.9 s
2.8 s
3.7 s
4.6 s
5.6 s
6.5 s
7.4 s
Speed
Mobile performance score: 47
47/100Your mobile performance score is 47. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.8 s
A phone's processor spends 7.8 s on main-thread work while loading, 4.4 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 (Google Tag Manager, heatmap.com and Facebook and others), adding 44.2 MB and 1.8 s of main-thread time.
Shopify adds 201 ms
201 msShopify costs a phone 201 ms of main-thread work and 42.8 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
150 ms · 1,011 KiB38 files are served with short cache lifetimes, so returning visitors download them again (1,011 KiB).
Reduce unused JavaScript
230 ms · 854 KiBAbout 854 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 230 ms faster on a phone.
Improve image delivery
1.0 MB24 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 780 ms
780 msGoogle Tag Manager costs a phone 780 ms of main-thread work and 570 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.
Render-blocking requests
700 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
2,989 HTML elements
The page has 2,989 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 296 ms. During a long task the page ignores taps.
gotolstoy.com adds 82 ms
82 msgotolstoy.com costs a phone 82 ms of main-thread work and 294 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.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Legacy JavaScript
65 KiBPolyfills for old browsers add 65 KiB JavaScript that modern phones do not need.
Reduce unused CSS
28 KiBAbout 28 KiB of CSS is downloaded but never applied on this page.
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.
Minify JavaScript
5 KiB5 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 13 ms
13 msYour server sent the HTML in 13 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.
Time to Interactive: 31.3 s
31.3 sThe page becomes fully interactive after 31.3 s. Good is under 3.8 s.
Speed Index: 14.0 s
14.0 sVisually, the page fills in at 14.0 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 5.4 s
5.4 sYour largest element takes 5.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Holiday 2026”.
Total Blocking Time: 1.0 s
1.0 sScripts block taps and scrolling for 1.0 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.6 s
2.6 sReal visitors wait 2.6 s for the largest content to appear (75th percentile). Good is under 2.5 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) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 170 ms to 184 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user INP: 129 ms
129 msReal visitors wait 129 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.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: 738 ms
738 msReal visitors wait 738 ms for your server to start answering (75th percentile). Good is under 800 ms.
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.057
0.057The layout barely moves while loading (CLS 0.057, good is under 0.1).
Images and page weight
Page weight: 51.2 MB in 437 requests
51.2 MBYour homepage downloads 51.2 MB in 437 requests on a phone: media 44.6 MB (15), scripts 2.6 MB (133) and images 2.3 MB (43). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
08-11_CobbleStone_Hero_Mobile_A.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 below the first screen load straight away
1 image further down the page (44 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 14.5 g of CO₂ per visit
14.50 gBy the Sustainable Web Design model, a visit to your homepage emits about 14.50 g of CO₂e: 1739.9 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
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
43 text elements with low contrast
43 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
9 images without alt text
9 images have no alt text, which hurts accessibility and image search.
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.
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.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails 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.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 56 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
175 internal links, 7 external
The homepage links to 175 pages on julievos.com and 7 external pages.
7 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Designed in New York City, Julie Vos fashion jewelry is made using semi-precious gemstones, pearl and fused glass, hand…”.
Title: 36 characters
Your title is a healthy 36 characters: “Fashion Designer Jewelry | Julie Vos”.
Canonical URL set
The canonical URL is https://www.julievos.com/.
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.julievos.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 (607 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.julievos.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
3 pages without a meta description
https://www.julievos.com/collections/breast-cancer-awareness, https://www.julievos.com/collections/nature and https://www.julievos.com/collections/symbolic-jewels have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.julievos.com/collections/breast-cancer-awareness has no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.julievos.com/collections/nature took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 78 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
1 broken image
1 image failed to load on a phone, for example https://p.alocdn.com/c/opmyshow/a/etarget/p.gif?label=julielindsey.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Cannot read properties of null (reading 'cloneNode')”.
2 checks passed
Tap targets are thumb-sized
25 of 29 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
About 251 words of copy
The homepage carries about 251 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 NOW” and “SHOP COLLECTION >”.
28 calls to action
The homepage has 28 calls to action, for example “SHOP”, “Shop All” and “Shop Tanzanite Blue”.
5 short forms
5 short forms (2 fields at most) are right on the homepage.
Social proof on the page
Social proof on the homepage: 10 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Ads and 2 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.
52 cookies set on arrival
52Opening the homepage sets 52 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.
66 other companies contacted
Loading the homepage contacts 66 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 julievos.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Analytics
- Google Tag Manager
- Hosting
- Shopify
Company
- Headquarters
- New York
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on julievos.com, including 19 speed issues and 1 SEO issue. 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.