somethingnicecompany.com website review

A phone's processor spends 27.7 s on main-thread work while loading, 9.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

replocdn.com costs a phone 1.4 s of main-thread work and 2.7 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Your mobile performance score is 33. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

The page has 4,162 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

8 third-party services load with your homepage (replocdn.com, Shopify and alia-prod.com and others), adding 69.9 MB and 3.8 s of main-thread time.

Shopify costs a phone 695 ms of main-thread work and 64.1 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.

About 1.4 MB of JavaScript is downloaded but never used on this page.

17 images could be 1,022 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

3 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

alia-prod.com costs a phone 538 ms of main-thread work and 1,006 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.

rebuyengine.com costs a phone 504 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.

20 long tasks block the main thread while loading, the longest for 433 ms. During a long task the page ignores taps.

23 files are served with short cache lifetimes, so returning visitors download them again (378 KiB).

Klaviyo costs a phone 305 ms of main-thread work and 501 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.

About 96 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.

Polyfills for old browsers add 130 KiB JavaScript that modern phones do not need.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

36 KiB could be saved by minifying CSS.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

5 KiB could be saved by minifying JavaScript.

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.

Visually, the page fills in at 38.1 s (Speed Index). Good is under 3.4 s.

The page becomes fully interactive after 173.2 s. Good is under 3.8 s.

Scripts block taps and scrolling for 3.1 s in total while the page loads. Good is under 200 ms.

Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.

Real visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.

Real visitors wait 812 ms for your server to start answering (75th percentile). Good is under 800 ms.

The first text or image appears after 2.5 s on a phone. Good is under 1.8 s.

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.9 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 71.7 MB in 480 requests on a phone: media 63.0 MB (16), scripts 4.2 MB (172) and other files 1.8 MB (208). Under 2 MB keeps phones on slow connections fast.

10 images further down the page (492 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

3 images are downloaded at several times the size a phone draws them, for example 1d0e7d73-98c3-4590-a539-a44262388c66 at 1,080 px wide, shown at 300 px. Resized copies would save about 53 KiB.

By the Sustainable Web Design model, a visit to your homepage emits about 20.33 g of CO₂e: 2439.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

Elements must only use permitted ARIA attributes: 30 elements on the page fail this check, rated serious by axe-core.

21 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

6 tap targets are too small or too close together to hit reliably with a finger.

ARIA input fields must have an accessible name: 5 elements on the page fail this check, rated serious by axe-core.

ARIA toggle fields must have an accessible name: 5 elements on the page fail this check, rated serious by axe-core.

ARIA commands must have an accessible name: 3 elements on the page fail this check, rated serious by axe-core.

Interactive controls must not be nested: 3 elements on the page fail this check, rated serious by axe-core.

14 images have no alt text, which hurts accessibility and image search.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 elements on the page fail this check, rated moderate by axe-core.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

Elements marked as presentational should be consistently ignored: 30 elements on the page fail this check, rated minor by axe-core.

ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (1 element).

Your title is only 14 characters: “Something Nice”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is 259 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 51 pages on somethingnicecompany.com and 3 external pages.

The HTML your server sends has 510 of the 1,477 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

https://somethingnicecompany.com/collections/new-arrivals, https://somethingnicecompany.com/collections/best-sellers and https://somethingnicecompany.com/collections/refills-replacements have no meta description, so Google writes the search snippet from whatever text it finds.

https://somethingnicecompany.com/pages/build-your-bundle, https://somethingnicecompany.com/collections/new-arrivals, https://somethingnicecompany.com/collections/best-sellers, https://somethingnicecompany.com/collections/kits, https://somethingnicecompany.com/products/zero-pro-toothpaste and https://somethingnicecompany.com/products/halo-gum and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://somethingnicecompany.com/pages/build-your-bundle, https://somethingnicecompany.com/products/zero-pro-toothpaste, https://somethingnicecompany.com/products/halo-gum, https://somethingnicecompany.com/products/aquaclean-duo, https://somethingnicecompany.com/products/zero-toothpaste and https://somethingnicecompany.com/products/lumismart-whitening-strips and 2 others 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.

We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.

3 images failed to load on a phone, for example https://files.alia-prod.com/Zerozero.webp-1755121028282.

25 of 79 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

The homepage carries about 1,477 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 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.

Opening the homepage sets 29 cookies (measured from a US location before any click).

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.

Loading the homepage contacts 54 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.