Website review, no card needed
droplette.io website review
Visit site (opens in a new tab)Reviewed 5 November 202642 issues · 87 checks
This review found 42 issues worth fixing on droplette.io, 20 of them high impact, across 87 checks. The most urgent: reduce unused JavaScript. 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- #62,709 of 125,377 reviewed websitesbeats 45%
- #40,760 of 70,167 online storesbeats 36%
- #38,906 of 63,757 Shopify storesbeats 33%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.3 s |
| May 23, 2026 | 2.3 s |
| May 30, 2026 | 2.1 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 2.3 s |
| Jul 11, 2026 | 2.4 s |
| Jul 18, 2026 | 2.5 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.4 s |
| Aug 8, 2026 | 2.5 s |
| Aug 15, 2026 | 2.1 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.3 s |
| Oct 10, 2026 | 1.4 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 131 ms |
| May 23, 2026 | 129 ms |
| May 30, 2026 | 120 ms |
| Jun 6, 2026 | 125 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 137 ms |
| Jun 27, 2026 | 143 ms |
| Jul 4, 2026 | 144 ms |
| Jul 11, 2026 | 145 ms |
| Jul 18, 2026 | 155 ms |
| Jul 25, 2026 | 147 ms |
| Aug 1, 2026 | 152 ms |
| Aug 8, 2026 | 157 ms |
| Aug 15, 2026 | 152 ms |
| Aug 22, 2026 | 170 ms |
| Aug 29, 2026 | 170 ms |
| Sep 5, 2026 | 171 ms |
| Sep 12, 2026 | 178 ms |
| Sep 19, 2026 | 162 ms |
| Sep 26, 2026 | 161 ms |
| Oct 3, 2026 | 162 ms |
| Oct 10, 2026 | 170 ms |
| Oct 17, 2026 | 182 ms |
| Oct 24, 2026 | 186 ms |
| Oct 31, 2026 | 178 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
1.9 s
3.9 s
5.8 s
7.8 s
9.7 s
11.6 s
13.6 s
15.5 s
Speed
Reduce unused JavaScript
7.6 s · 1.6 MBAbout 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 7.6 s faster on a phone.
Use efficient cache lifetimes
2.0 s · 842 KiB22 files are served with short cache lifetimes, so returning visitors download them again (842 KiB).
Render-blocking requests
1.4 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 7.4 s
A phone's processor spends 7.4 s on main-thread work while loading, 3.9 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, ZenDesk and poweredbyhue.app and others), adding 3.9 MB and 2.6 s of main-thread time.
Improve image delivery
400 ms · 1.3 MB16 images could be 1.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 400 ms faster on a phone.
Google Tag Manager adds 662 ms
662 msGoogle Tag Manager costs a phone 662 ms of main-thread work and 1.2 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.
ZenDesk adds 657 ms
657 msZenDesk costs a phone 657 ms of main-thread work and 950 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.
poweredbyhue.app adds 404 ms
404 mspoweredbyhue.app costs a phone 404 ms of main-thread work and 920 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.
19 long tasks on the main thread
19 long tasks block the main thread while loading, the longest for 280 ms. During a long task the page ignores taps.
Hotjar adds 270 ms
270 msHotjar costs a phone 270 ms of main-thread work and 65 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.
1,951 HTML elements
The page has 1,951 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Klaviyo adds 146 ms
146 msKlaviyo costs a phone 146 ms of main-thread work and 322 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
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
31 KiBPolyfills for old browsers add 31 KiB JavaScript that modern phones do not need.
Reduce unused CSS
13 KiBAbout 13 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
7 KiB7 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: 7 ms
7 msYour server sent the HTML in 7 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: 25.9 s
25.9 sYour largest element takes 25.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 39.5 s
39.5 sThe page becomes fully interactive after 39.5 s. Good is under 3.8 s.
Speed Index: 13.4 s
13.4 sVisually, the page fills in at 13.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 4.7 s
4.7 sThe first text or image appears after 4.7 s on a phone. Good is under 1.8 s.
Total Blocking Time: 819 ms
819 msScripts block taps and scrolling for 819 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 40% slower for real visitors
+40%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 131 ms to 178 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user TTFB: 1.0 s
1.0 sReal visitors wait 1.0 s for your server to start answering (75th percentile). Good is under 800 ms.
16 images without width and height
16 images have no width and height attributes, so the layout jumps as each one loads.
6 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 162 ms
162 msReal visitors wait 162 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Largest content (LCP) got 23% faster for real visitors
-23%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.3 s to 1.8 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: 19.5 MB in 515 requests
19.5 MBYour homepage downloads 19.5 MB in 515 requests on a phone: media 12.0 MB (12), scripts 4.0 MB (145) and images 1.8 MB (28). Under 2 MB keeps phones on slow connections fast.
4 images far larger than shown
536 KiB4 images are downloaded at several times the size a phone draws them, for example Radiant-Detox-BA.jpg at 1,800 px wide, shown at 362 px. Resized copies would save about 536 KiB.
5 images below the first screen load straight away
5 images further down the page (841 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.5 g of CO₂ per visit
5.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.54 g of CO₂e: 664.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
Interactive controls must not be nested (2 elements)
Interactive controls must not be nested: 2 elements on the page fail this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
12 images without alt text
12 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail 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.
Headings skip levels
Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.
1 checks passed
47 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: 47 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.
86 internal links, 4 external
The homepage links to 86 pages on droplette.io and 4 external pages.
7 checks passed
Meta description: 103 characters
Your meta description is 103 characters: “We create serums with pharmaceutical-grade ingredients amplified with 20X more absorption vs. topicals.”.
Title: 55 characters
Your title is a healthy 55 characters: “Droplette - Skincare On A Deeper Level | Droplette Inc.”.
Canonical URL set
The canonical URL is https://droplette.io/.
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://droplette.io/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,036 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://droplette.io/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://droplette.io/products/3-month-starter-set 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://droplette.io/products/3-month-starter-set all use the title “Droplette - Skincare On A Deeper Level | Droplette Inc.”. Search engines can't tell which page to show for a search, so each competes with the others.
5 pages without a meta description
https://droplette.io/policies/shipping-policy, https://droplette.io/collections/dry-skin, https://droplette.io/collections/anti-aging, https://droplette.io/collections/dark-spots and https://droplette.io/pages/how-it-works-1 have no meta description, so Google writes the search snippet from whatever text it finds.
4 pages without an H1
https://droplette.io/products/3-month-starter-set, https://droplette.io/pages/how-it-works-1, https://droplette.io/pages/how-it-works and https://droplette.io/pages/faq 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 29 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
5 broken images
5 images failed to load on a phone, for example https://hue-admin-dev.s3.amazonaws.com/assets/skin-twin-assets/1769118964543-thumbnail-7163872-20260122-215603-20260122-215604.webp.
12 small tap targets
12 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
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”.
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 460 words of copy
The homepage carries about 460 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 Started” and “Shop All”.
16 calls to action
The homepage has 16 calls to action, for example “Shop”, “Shop All” and “Get Started”.
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: 39 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and Microsoft Clarity.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Klaviyo and 4 mores (measured from a US location before any click). A consent tool (Ketch) is installed; check it blocks these until visitors agree where the law requires it.
24 cookies set on arrival
24Opening the homepage sets 24 cookies (measured from a US location before any click).
61 other companies contacted
Loading the homepage contacts 61 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Ketch
A consent management tool (Ketch) loads with the page.
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 droplette.io, 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
Seowill Redirects · Klaviyo Email Marketing Sms · Impact Com · Yotpo Product Reviews · Font Picker · Microsoft Clarity · rechargecdn.com · electricsms.com · rakutenadvertising.io
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
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Analytics | Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Hiring
- Hiring
- 1 open role
- Job board
- bamboohr
Company
- Headquarters
- Boston
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on droplette.io, including 23 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.