elnoexperto.com website review

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

220 files are served with short cache lifetimes, so returning visitors download them again (3.1 MB).

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

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

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

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

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

The HTML itself could arrive about 800 ms sooner: redirects, a slow server response or missing compression delay everything after it.

Reduce initial server response time. Google estimates savings of 775 ms on a phone.

3 third-party services load with your homepage (Google Fonts, rstheme.com and Gravatar), adding 2.8 MB and 3 ms of main-thread time.

rstheme.com costs a phone 0 ms of main-thread work and 2.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.

About 268 KiB of JavaScript is downloaded but never used on this page.

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

Your server takes 875 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

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

44 KiB could be saved by minifying JavaScript.

19 KiB could be saved by minifying CSS.

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

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

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

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

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

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

14 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 7.2 MB in 230 requests on a phone: images 5.6 MB (56), fonts 573 KiB (11) and scripts 566 KiB (52). Under 2 MB keeps phones on slow connections fast.

feature-man-img.png weighs 1.8 MB. On a phone connection a single image that size takes seconds.

1 image is downloaded at several times the size a phone draws it, for example feature-man-img.png at 1,022 px wide, shown at 263 px. Resized copies would save about 754 KiB.

6 images (2.7 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

3 images further down the page (719 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 2.05 g of CO₂e: 245.6 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.

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

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

Your title is only 13 characters: “El No Experto”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

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 101 pages on elnoexperto.com and 7 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://elnoexperto.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://elnoexperto.com/home, https://elnoexperto.com/home-two, https://elnoexperto.com/home-three, https://elnoexperto.com/home-five, https://elnoexperto.com/home-six and https://elnoexperto.com/home-seven and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://elnoexperto.com/home-nine and https://elnoexperto.com/home-eleven have no <h1> headline, so visitors and search engines get no clear main topic.

https://elnoexperto.com/home, https://elnoexperto.com/home-two, https://elnoexperto.com/home-three, https://elnoexperto.com/home-five, https://elnoexperto.com/home-six and https://elnoexperto.com/home-seven and 6 others took over 3 s to send their HTML from our server.

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

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Large scripts ship without source maps.

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

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

The homepage carries about 691 words of visible text.

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