Website review, no card needed
trysorelle.com website review
Visit site (opens in a new tab)Reviewed 7 November 202640 issues · 84 checks
This review found 40 issues worth fixing on trysorelle.com, 11 of them high impact, across 84 checks. The most urgent: avoid multiple page redirects. 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
73C- #90,688 of 122,656 reviewed websitesbeats 23%
- #56,670 of 69,234 online storesbeats 15%
- #53,059 of 63,054 Shopify storesbeats 13%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.1 s |
| May 23, 2026 | 3.1 s |
| May 30, 2026 | 3.2 s |
| Jun 6, 2026 | 3.2 s |
| Jun 13, 2026 | 3.3 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.2 s |
| Jul 4, 2026 | 3.2 s |
| Jul 11, 2026 | 3.1 s |
| Jul 18, 2026 | 3.1 s |
| Jul 25, 2026 | 3.1 s |
| Aug 1, 2026 | 3.1 s |
| Aug 8, 2026 | 3.1 s |
| Aug 15, 2026 | 3.2 s |
| Aug 22, 2026 | 3.1 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.0 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.2 s |
| Sep 26, 2026 | 3.3 s |
| Oct 3, 2026 | 3.3 s |
| Oct 10, 2026 | 3.2 s |
| Oct 17, 2026 | 2.9 s |
| Oct 24, 2026 | 2.7 s |
| Oct 31, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 203 ms |
| May 23, 2026 | 204 ms |
| May 30, 2026 | 211 ms |
| Jun 6, 2026 | 218 ms |
| Jun 13, 2026 | 226 ms |
| Jun 20, 2026 | 237 ms |
| Jun 27, 2026 | 245 ms |
| Jul 4, 2026 | 247 ms |
| Jul 11, 2026 | 239 ms |
| Jul 18, 2026 | 236 ms |
| Jul 25, 2026 | 231 ms |
| Aug 1, 2026 | 234 ms |
| Aug 8, 2026 | 254 ms |
| Aug 15, 2026 | 256 ms |
| Aug 22, 2026 | 257 ms |
| Aug 29, 2026 | 271 ms |
| Sep 5, 2026 | 269 ms |
| Sep 12, 2026 | 267 ms |
| Sep 19, 2026 | 274 ms |
| Sep 26, 2026 | 261 ms |
| Oct 3, 2026 | 247 ms |
| Oct 10, 2026 | 247 ms |
| Oct 17, 2026 | 245 ms |
| Oct 24, 2026 | 247 ms |
| Oct 31, 2026 | 237 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
Avoid multiple page redirects
3.9 sThe page goes through 1 redirect before it starts loading, costing about 3.9 s. Link and advertise the final URL directly.
Main-thread work: 14.1 s
A phone's processor spends 14.1 s on main-thread work while loading, 2.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce unused JavaScript
900 ms · 274 KiBAbout 274 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
900 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Klaviyo and Google Tag Manager and others), adding 1.4 MB and 707 ms of main-thread time.
Shopify adds 213 ms
213 msShopify costs a phone 213 ms of main-thread work and 762 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.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 280 ms. During a long task the page ignores taps.
2,348 HTML elements
The page has 2,348 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 183 ms
183 msKlaviyo costs a phone 183 ms of main-thread work and 316 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.
Use efficient cache lifetimes
150 ms · 58 KiB12 files are served with short cache lifetimes, so returning visitors download them again (58 KiB).
Legacy JavaScript
150 ms · 33 KiBPolyfills for old browsers add 33 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Minify JavaScript
43 KiB43 KiB could be saved by minifying JavaScript.
Reduce unused CSS
13 KiBAbout 13 KiB of CSS is downloaded but never applied on this page.
Minify CSS
10 KiB10 KiB could be saved by minifying CSS.
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: 29 ms
29 msYour server sent the HTML in 29 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: 13.7 s
13.7 sYour largest element takes 13.7 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.3 s
21.3 sThe page becomes fully interactive after 21.3 s. Good is under 3.8 s.
Speed Index: 6.4 s
6.4 sVisually, the page fills in at 6.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user LCP: 4.0 s
4.0 sReal visitors wait 4.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 394 ms
394 msReal visitors wait 394 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Total Blocking Time: 425 ms
425 msScripts block taps and scrolling for 425 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.
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 203 ms to 237 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 0.9 s
0.9 sReal visitors see the first content after 0.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 298 ms
298 msReal visitors wait 298 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 13% faster for real visitors
-13%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.1 s to 2.6 s 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: 4.1 MB in 462 requests
4.1 MBYour homepage downloads 4.1 MB in 462 requests on a phone: other files 1.7 MB (283), scripts 1.4 MB (135) and fonts 489 KiB (14). Under 2 MB keeps phones on slow connections fast.
5 images in older formats
5 images (373 KiB) 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 1.2 g of CO₂ per visit
1.17 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.17 g of CO₂e: 140.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
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
Images must have alternative text (1 element)
Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (28 elements)
All page content should be contained by landmarks: 28 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
1 checks passed
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 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
Title is short (17 characters)
Your title is only 17 characters: “Sorelle – Sorelle”. Between 30 and 65 characters leaves room to say what you do and for whom.
No XML sitemap
No XML sitemap at https://trysorelle.com/sitemap.xml, so Google discovers your pages only by following links.
One H1 headline
Your <h1> is empty.
16 internal links, 7 external
The homepage links to 16 pages on trysorelle.com and 7 external pages.
5 checks passed
Meta description: 150 characters
Your meta description is 150 characters: “Sorelle Drops - the glow you drink. Tanning drops you drink, and oral glutathione brightening drops. Take control of yo…”.
Canonical URL set
The canonical URL is https://trysorelle.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.
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 (636 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://trysorelle.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://trysorelle.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://trysorelle.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
6 pages without a meta description
https://trysorelle.com/products/result, https://trysorelle.com/pages/faq, https://trysorelle.com/pages/influencer, https://trysorelle.com/customer_authentication/redirect, https://trysorelle.com/pages/lp1 and https://trysorelle.com/pages/brightening-lp1 have no meta description, so Google writes the search snippet from whatever text it finds.
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://trysorelle.com/pages/lp1, whose canonical is https://trysorelle.com/pages/lp7. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
7 pages without an H1
https://trysorelle.com/products/sorelle-brightening-drops-the-glow-you-drink, https://trysorelle.com/pages/science, https://trysorelle.com/pages/tan-timeline, https://trysorelle.com/pages/faq, https://trysorelle.com/customer_authentication/redirect and https://trysorelle.com/pages/lp1 and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
3 pages with very little text
https://trysorelle.com/products/sorelle-tanning-drops-the-glow-you-drink, https://trysorelle.com/products/sorelle-brightening-drops-the-glow-you-drink and https://trysorelle.com/pages/brightening-lp1 have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
10 internal pages checked
We fetched 10 pages linked from your homepage and read each the way a search engine does.
2 checks passed
Linked pages load
All 10 pages we checked loaded without an error.
Titles are unique
Every page we checked has its own title.
Best practices
6 JavaScript errors while loading
6 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
10 of 12 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
About 573 words of copy
The homepage carries about 573 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 MY GLOW”.
5 calls to action
The homepage has 5 calls to action, for example “SHOP TANNING DROPS”, “SHOP BRIGHTENING DROPS” and “GET MY GLOW”.
10 short forms
10 short forms (1 field at most) are right on the homepage.
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
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
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Klaviyo, Meta Pixel and Snap 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.
26 cookies set on arrival
26Opening the homepage sets 26 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.
42 other companies contacted
Loading the homepage contacts 42 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 trysorelle.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 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Judge Me Reviews · Gempages Builder · Monster Cart Upsell Free Gifts · Kaching Bundles · Klaviyo Email Marketing Sms · Triplewhale · Bucks · Microsoft Clarity · Seal Subscriptions · Gempages Cro · Monster Upsells · googleapis.com · archive-digger.com
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
- Tailwind CSS
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on trysorelle.com, including 19 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.