geaprstore.com website review

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

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

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

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

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 450 ms.

8 third-party services load with your homepage (Google Tag Manager, Directed Edge and Shopify and others), adding 450 KiB and 304 ms of main-thread time.

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

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

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

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.

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

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

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

Real visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Your homepage downloads 2.5 MB in 278 requests on a phone: other files 1.0 MB (199), scripts 659 KiB (41) and images 572 KiB (29). Under 2 MB keeps phones on slow connections fast.

IMG_0986.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

By the Sustainable Web Design model, a visit to your homepage emits about 0.70 g of CO₂e: 84.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: 1 element on the page fails this check, rated critical by axe-core.

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

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

Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.

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

Your title is 97 characters, so Google will cut it off around 60: “GE Appliances Store | Enseres del hogar y cocina en Puerto Rico – GE Appliances Puerto Ri…”.

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

There are 2 <h1> headlines (“GE Appliances Puerto Rico Store” and “GE Appliances Puerto Rico Store”). One clear main headline is easier for people and search engines.

The homepage links to 643 pages on geaprstore.com and 10 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.

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

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

5 errors were logged to the browser console while the page loaded, for example “Invalid or unexpected token”.

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

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

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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 1,269 words of visible text.

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