Website review, no card needed
suotstudio.com website review
Visit site (opens in a new tab)Reviewed 12 November 202629 issues · 81 checks
This review found 29 issues worth fixing on suotstudio.com, 10 of them high impact, across 81 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
84B- #19,850 of 109,350 reviewed websitesbeats 77%
- #12,897 of 61,859 online storesbeats 73%
- #12,521 of 56,401 Shopify storesbeats 71%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.9 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.7 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.9 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.3 s |
| Aug 29, 2026 | 2.2 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.0 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.7 s |
| Oct 3, 2026 | 1.6 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.5 s |
| Nov 7, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 180 ms |
| May 30, 2026 | 178 ms |
| Jun 6, 2026 | 165 ms |
| Jun 13, 2026 | 163 ms |
| Jun 20, 2026 | 163 ms |
| Jun 27, 2026 | 176 ms |
| Jul 4, 2026 | 172 ms |
| Jul 11, 2026 | 170 ms |
| Jul 18, 2026 | 181 ms |
| Jul 25, 2026 | 169 ms |
| Aug 1, 2026 | 179 ms |
| Aug 8, 2026 | 196 ms |
| Aug 15, 2026 | 198 ms |
| Aug 22, 2026 | 207 ms |
| Aug 29, 2026 | 227 ms |
| Sep 5, 2026 | 219 ms |
| Sep 12, 2026 | 217 ms |
| Sep 19, 2026 | 214 ms |
| Sep 26, 2026 | 198 ms |
| Oct 3, 2026 | 205 ms |
| Oct 10, 2026 | 192 ms |
| Oct 17, 2026 | 197 ms |
| Oct 24, 2026 | 185 ms |
| Oct 31, 2026 | 181 ms |
| Nov 7, 2026 | 179 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
Speed
Render-blocking requests
1.5 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Main-thread work: 4.6 s
A phone's processor spends 4.6 s on main-thread work while loading, 2.0 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, Klaviyo and Clarity and others), adding 1.8 MB and 1.2 s of main-thread time.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
250 ms · 479 KiB14 images could be 479 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 250 ms faster on a phone.
Reduce unused JavaScript
686 KiBAbout 686 KiB of JavaScript is downloaded but never used on this page.
Google Tag Manager adds 554 ms
554 msGoogle Tag Manager costs a phone 554 ms of main-thread work and 725 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,151 HTML elements
The page has 2,151 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 177 ms
177 msKlaviyo costs a phone 177 ms of main-thread work and 345 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.
Reduce unused CSS
150 ms · 27 KiBAbout 27 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.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 166 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
91 KiB21 files are served with short cache lifetimes, so returning visitors download them again (91 KiB).
Legacy JavaScript
31 KiBPolyfills for old browsers add 31 KiB JavaScript that modern phones do not need.
Minify JavaScript
14 KiB14 KiB could be saved by minifying JavaScript.
Duplicated JavaScript
11 KiB11 KiB JavaScript is shipped twice across bundles.
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: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 22.7 s
22.7 sThe page becomes fully interactive after 22.7 s. Good is under 3.8 s.
Largest Contentful Paint: 5.6 s
5.6 sYour largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SILVER_PAPER_home_mobile_1080x1080_v1015.mp4”.
Speed Index: 6.2 s
6.2 sVisually, the page fills in at 6.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 600 ms
600 msScripts block taps and scrolling for 600 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.102
0.102The layout shifts by 0.102 while loading, so content jumps under the reader's thumb. Good is under 0.1.
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
+1%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 180 ms to 179 ms 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: 1.5 s
1.5 sReal visitors wait 1.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 180 ms
180 msReal visitors wait 180 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: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 690 ms
690 msReal visitors wait 690 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 16% faster for real visitors
-16%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 12.2 MB in 320 requests
12.2 MBYour homepage downloads 12.2 MB in 320 requests on a phone: media 8.0 MB (3), scripts 1.8 MB (107) and other files 1.1 MB (122). Under 2 MB keeps phones on slow connections fast.
About 3.5 g of CO₂ per visit
3.47 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.47 g of CO₂e: 415.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
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.
3 images without alt text
3 images have no alt text, which hurts accessibility and image search.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 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.
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.
21 links without text
21 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
51 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: 51 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
One H1 headline
Your <h1> is empty.
107 internal links, 7 external
The homepage links to 107 pages on suotstudio.com and 7 external pages.
7 checks passed
Meta description: 127 characters
Your meta description is 127 characters: “Modular jewelry to connect concepts and people through self-expression. Souled by Marta Tous. Complimentary Worldwide S…”.
Title: 59 characters
Your title is a healthy 59 characters: “SUOT STUDIO - An experimental jewelry project – SUOT Studio”.
Canonical URL set
The canonical URL is https://suotstudio.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://suotstudio.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 (711 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://suotstudio.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://suotstudio.com/collections/plates-conexiones-hidden is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
5 pages without a meta description
https://suotstudio.com/collections/new-in, https://suotstudio.com/collections/best-sellers, https://suotstudio.com/collections/plates-conexiones-hidden, https://suotstudio.com/collections/tooth-gems and https://suotstudio.com/collections/suot-piercings have no meta description, so Google writes the search snippet from whatever text it finds.
12 pages without an H1
https://suotstudio.com/collections/new-in, https://suotstudio.com/collections/best-sellers, https://suotstudio.com/collections/earcuffs, https://suotstudio.com/collections/earrings, https://suotstudio.com/collections/bracelets and https://suotstudio.com/collections/necklaces and 6 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 51 found) and read each the way a search engine does.
4 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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
4 JavaScript errors while loading
4 errors were 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
43 of 51 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.
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 462 words of copy
The homepage carries about 462 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: “GET YOUR CODE”.
3 calls to action
The homepage has 3 calls to action, for example “Contact us”, “Contact Us” and “Subscribe”.
4 short forms
4 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity, Hotjar and TikTok Pixel.
Direct contact links
Visitors can reach you directly: 0 phone links and 4 email links.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
28 cookies set on arrival
28Opening the homepage sets 28 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.
39 other companies contacted
Loading the homepage contacts 39 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 suotstudio.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 11 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Pandectes Gdpr · Microsoft Clarity · Fontify · Inbox · Klaviyo Email Marketing Sms · Wingify · Gdpr Cookie Consent · Promotion Popup Allnew · azureedge.net · amazonaws.com · Swym Wishlist Plus
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
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Hotjar | 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 29 issues on suotstudio.com, including 15 speed issues, 1 SEO issue 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.