halfpricedmacs.com website review

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

8 third-party services load with your homepage (Shopify, frontapp.com and Google Tag Manager and others), adding 4.1 MB and 2.1 s of main-thread time.

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

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

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

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

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

frontapp.com costs a phone 501 ms of main-thread work and 1.5 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 416 ms. During a long task the page ignores taps.

automizely.com costs a phone 166 ms of main-thread work and 381 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.

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

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

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

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

61 KiB could be saved by minifying JavaScript.

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.

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

2 KiB could be saved by minifying CSS.

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.

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

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

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

For real visitors the layout shifts by 0.23 (75th percentile). Good is under 0.1.

The layout shifts by 0.203 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

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

Your homepage downloads 7.9 MB in 508 requests on a phone: scripts 3.5 MB (213), other files 2.5 MB (222) and fonts 1.3 MB (12). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example Image_20_3d8d4d85-7f6d-4d89-ae81-ef156d41bf8a.jpg at 1,024 px wide, shown at 75 px. Resized copies would save about 54 KiB.

1 image further down the page (61 KiB) 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.23 g of CO₂e: 267.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 element use ARIA attributes their role does not allow, which confuses screen readers.

1 button has no accessible name, so screen readers announce just “button”.

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

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

Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 16 characters: “Half Priced Macs”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“halfpricedmacs” and “MacBook Airs & MacBook Pros Available at Discount…”). One clear main headline is easier for people and search engines.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 102 pages on halfpricedmacs.com and 11 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.

There is no https://halfpricedmacs.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

https://halfpricedmacs.com/pages/reviews, https://halfpricedmacs.com/pages/contact-us-1, https://halfpricedmacs.com/pages/faq, https://halfpricedmacs.com/pages/quiz, https://halfpricedmacs.com/collections/macbooks and https://halfpricedmacs.com/collections/macbook-airs and 1 other have no meta description, so Google writes the search snippet from whatever text it finds.

https://halfpricedmacs.com/pages/reviews, https://halfpricedmacs.com/pages/contact-us-1 and https://halfpricedmacs.com/pages/quiz have no <h1> headline, so visitors and search engines get no clear main topic.

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

6 errors were logged to the browser console while the page loaded, for example “Unexpected token '}'”.

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

Your longest form asks for 10 fields (0 required). Every extra field lowers completion.

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

The page uses urgency cues (a countdown or limited-time wording).

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