underlining.com website review

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

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

5 third-party services load with your homepage (replocdn.com, Shopify and shgcdn3.com and others), adding 878 KiB and 213 ms of main-thread time.

1 long task block the main thread while loading, the longest for 146 ms. During a long task the page ignores taps.

4 images could be 127 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 88 KiB of JavaScript is downloaded but never used on this page.

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

About 25 KiB of CSS is downloaded but never applied on this page.

14 KiB could be saved by minifying CSS.

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

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

51 images have no width and height attributes, so the layout jumps as each one loads.

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

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

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

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 has only about 199 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no form on the homepage, so every lead has to click through to another page first.