getawhiff.com website review

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

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

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

8 third-party services load with your homepage (Shopify, loox.io and productcustomizer.com and others), adding 3.1 MB and 1.3 s of main-thread time.

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

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

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

loox.io costs a phone 280 ms of main-thread work and 85 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 283 KiB of JavaScript is downloaded but never used on this page.

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

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

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

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

37 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 31 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.

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 CSS.

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

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

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

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

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

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

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.

Your homepage downloads 4.9 MB in 192 requests on a phone: images 2.9 MB (37), scripts 973 KiB (74) and other files 595 KiB (48). Under 2 MB keeps phones on slow connections fast.

8 images are downloaded at several times the size a phone draws them, for example HeatherT.png at 4,264 px wide, shown at 180 px. Resized copies would save about 918 KiB.

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

5 elements hidden from screen readers can still receive keyboard focus.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

All page content should be contained by landmarks: 2 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.

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

Your canonical URL points to dangleit.com, not getawhiff.com, so Google may credit that host instead.

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

There are 3 <h1> headlines (“.site-header__logo-image { height: 50px; }”, “35,000+ 5 Star Reviews Custom Air Fresheners” and “FAQs”). One clear main headline is easier for people and search engines.

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

2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 22 pages on getawhiff.com and 30 external pages.

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.

https://getawhiff.com/products/scent-sample, https://getawhiff.com/pages/faq-2 and https://getawhiff.com/pages/contact-us have no meta description, so Google writes the search snippet from whatever text it finds.

https://getawhiff.com/products/custom-air-freshener, https://getawhiff.com/products/scent-sample and https://getawhiff.com/pages/faq-2 have no <h1> headline, so visitors and search engines get no clear main topic.

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

4 errors were logged to the browser console while the page loaded, for example “Iframe not found.”.

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 11 fields (6 required). Every extra field lowers completion.

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 786 words of visible text.

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

Opening the homepage sets 14 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 38 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.