apluslift.com website review

About 404 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.3 s faster on a phone.

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

8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.0 s.

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

About 124 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

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

PayPal costs a phone 332 ms of main-thread work and 288 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.

8 third-party services load with your homepage (PayPal, Google Tag Manager and Shopify and others), adding 863 KiB and 476 ms of main-thread time.

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

7 KiB could be saved by minifying CSS.

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.

Your largest element takes 11.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “APlusLift HW-10KOH-A 10,000 LB 2-Post Over Head Heavy Duty …”.

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

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

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

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

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

Your homepage downloads 2.5 MB in 192 requests on a phone: scripts 896 KiB (46), other files 770 KiB (96) and images 478 KiB (31). Under 2 MB keeps phones on slow connections fast.

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

Images must have alternative text: 5 elements on the page fail this check, rated critical by axe-core.

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

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

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

1 link inside paragraphs relies on colour alone to stand out.

Some list items are not inside a list.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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

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

10 visible links have no text or label, so screen readers cannot say where they go.

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

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

Structured data found (Organization) but with 1 problem, for example “ld+json block 2 is not valid JSON (Unexpected non-whitespace character after JSON at position 3)”.

3 links have no real href, so search engines can't follow them.

Your <h1> is empty.

The homepage links to 66 pages on apluslift.com and 3 external pages.

https://apluslift.com/collections/2-post-lifts, https://apluslift.com/collections/4-post-parking-and-alignment-lifts, https://apluslift.com/collections/scissor-lifts, https://apluslift.com/collections/car-lift-parts, https://apluslift.com/collections/2-post-car-lift-parts and https://apluslift.com/collections/4-post-lifts-and-jacks-parts and 2 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

2 errors were logged to the browser console while the page loaded, for example “Uncaught (in promise) TypeError: Cannot convert undefined or null to object”.

1 image is served at too low a resolution for sharp phone screens.

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 homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage has only about 163 words of visible text; thin pages give Google and first-time buyers little to go on.

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

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