mylaughland.com website review

11 images could be 5.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 26.4 s faster on a phone.

Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.

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

About 23 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.

8 third-party services load with your homepage (Snapchat, Shopify and bc86mdtrk.com and others), adding 356 KiB and 182 ms of main-thread time.

Polyfills for old browsers add 23 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

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

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

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 103 ms to 127 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

2 images weigh 14.1 MB together. On a phone connection a single image that size takes seconds.

Your homepage downloads 7.8 MB in 216 requests on a phone: images 6.0 MB (20), other files 673 KiB (84) and scripts 624 KiB (77). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Laughland_Homepage_Lilac.gif at 2,000 px wide, shown at 390 px. Resized copies would save about 4.3 MB.

2 images (14.1 MB) 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.

1 image further down the page (7.5 MB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

7 buttons have no accessible name, so screen readers announce just “button”.

<dl> elements must only directly contain properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements: 9 elements on the page fail this check, rated serious by axe-core.

<dt> and <dd> elements must be contained by a <dl>: 9 elements on the page fail this check, rated serious by axe-core.

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

All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

1 visible link has no text or label, so screen readers cannot say where it goes.

Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.

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

Your title is 70 characters, so Google will cut it off around 60: “Laughland | Sensitivity-Free Teeth Whitening – Laughland Sciences Inc.”.

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

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

The homepage links to 28 pages on mylaughland.com and 6 external pages.

Your Organization JSON-LD is missing logo, description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

https://www.mylaughland.com/pages/science-of-teeth-whitening, https://www.mylaughland.com/pages/whitening-101, https://www.mylaughland.com/pages/faq, https://www.mylaughland.com/pages/utm_partner, https://www.mylaughland.com/policies/privacy-policy and https://www.mylaughland.com/policies/refund-policy and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mylaughland.com/products/refill-kit has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 11 pages linked from your homepage and read each the way a search engine does.

1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=1f1094ca-dc48-4ddf-b963-d9f3ff390629&referrer=&landingpage=https%3A%2F%2Fwww.mylaughland.com%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20OS.

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

1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://a.klaviyo.com/media/css/public/klaviyo_subscribe.css' from origin 'https://www.myl…”.

Chrome logged issues while loading the page (“Cookie”).

Social proof on the homepage: 43 testimonial or review blocks. 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.

Your longest form asks for 28 fields (3 required). Every extra field lowers completion.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 383 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 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 27 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 42 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.