efe.com.pe website review

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

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

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

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

Google Tag Manager costs a phone 1.4 s of main-thread work and 715 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

About 137 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

Your mobile performance score is 26. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

62 images could be 5.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google Tag Manager, Hubspot and TikTok and others), adding 1.9 MB and 3.7 s of main-thread time.

20 long tasks block the main thread while loading, the longest for 1.0 s. During a long task the page ignores taps.

Hubspot costs a phone 852 ms of main-thread work and 312 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.

TikTok costs a phone 545 ms of main-thread work and 292 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.

Facebook costs a phone 486 ms of main-thread work and 299 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.

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

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

Real visitors see the first content after 4.9 s (75th percentile). Good is under 1.8 s.

Real visitors wait 4.2 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

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

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

Real visitors wait 495 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

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

Your homepage downloads 25.6 MB in 495 requests on a phone: images 22.4 MB (150), scripts 2.4 MB (223) and HTML 396 KiB (3). Under 2 MB keeps phones on slow connections fast.

12 images weigh 11.0 MB together. On a phone connection a single image that size takes seconds.

efe-slider-b2c-02-computo-02_51.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).

1 image is downloaded at several times the size a phone draws it, for example DORMITORIOS_1.png at 321 px wide, shown at 62 px. Resized copies would save about 81 KiB.

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

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

1 tap target is too small or too close together to hit reliably with a finger.

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

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

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

There are 2 <h1> headlines (“Tiendas EFE: Tecnología y Electrodomésticos Online” and “Multiservicios”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 1,227 pages on efe.com.pe and 5 external pages.

Your homepage links to /wishlist, which answers with an error. Visitors hit a dead end and search engines drop it.

/catalog/product_compare, /evalua-credito-efectiva, /localizador-tiendas and /blog use the same meta description. A description written for each page earns more clicks.

/evalua-credito-efectiva has no <h1> headline, so visitors and search engines get no clear main topic.

/estilo-de-vida/trabajo-y-estudio-en-casa/tablets.html took over 3 s to send its HTML from our server.

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

4 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://script.google.com/macros/s/AKfycbz2GLAo_L5PrXVZcMxCP6sToBVisxB8vcYdmynxoFs6_m-Igr6j-1BD7QT7…”.

Chrome logged issues while loading the page (“Content security policy”).

1 link from your homepage to your own site is broken, for example https://www.efe.com.pe/customer/account/ (network).

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

efe.com.pe has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

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

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

Social proof on the homepage: 3 trust badges. 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,417 words of visible text.

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

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel and 2 mores (measured from a US location before any click). A consent tool (Didomi) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 29 cookies (measured from a US location before any click).

Loading the homepage contacts 46 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.