evagiahan.com website review

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

26 images could be 859 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.9 s faster on a phone.

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

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

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

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

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

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

6 third-party services load with your homepage (YouTube, Other Google APIs/SDKs and Google Fonts and others), adding 1.7 MB and 349 ms of main-thread time.

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

YouTube costs a phone 341 ms of main-thread work and 1.1 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.

Google Fonts costs a phone 1 ms of main-thread work and 362 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.

17 KiB could be saved by minifying CSS.

11 KiB could be saved by minifying JavaScript.

Polyfills for old browsers add 8 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 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 14.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image. Most of its time is resource load delay (9.1 s).

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

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

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

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

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 4.9 MB in 168 requests on a phone: images 2.8 MB (43), scripts 1.2 MB (55) and fonts 441 KiB (16). Under 2 MB keeps phones on slow connections fast.

lien-he-600x71.jpg 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).

18 images (1,006 KiB) 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 (277 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 1.39 g of CO₂e: 166.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

8 buttons have no accessible name, so screen readers announce just “button”.

1 dropdown has no label.

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

ARIA input fields must have an accessible name: 4 elements on the page fail this check, rated serious by axe-core.

Interactive controls must not be nested: 4 elements on the page fail this check, rated serious by axe-core.

ARIA progressbar nodes must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

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

5 images have no alt text, which hurts accessibility and image search.

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

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

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

3 form fields have no label, so screen readers announce an empty box and autofill guesses.

Headings skip levels (h2 → h5, h2 → h5 and h1 → h3), 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.

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

Structured data found (Product and WebSite) but with 8 problems, for example “Product: no offers (price) block”.

There is no robots.txt at evagiahan.com/robots.txt, the first file search crawlers ask for.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 902 pages on evagiahan.com and 21 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://evagiahan.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://evagiahan.com/gioi-thieu, https://evagiahan.com/lien-he, https://evagiahan.com/danh-muc-san-pham/son-duong-moi-handmade-cao-cap, https://evagiahan.com/san-pham/son-duong-moi-handmade-cao-cap-lipstick-mau-do-tuoi, https://evagiahan.com/san-pham/son-duong-moi-handmade-cao-cap-lipstick-mau-do-cam and https://evagiahan.com/san-pham/son-duong-moi-handmade-cao-cap-lipstick-mau-do-hong and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://evagiahan.com/san-pham/son-duong-moi-handmade-cao-cap-lipstick-mau-do-tuoi, https://evagiahan.com/san-pham/son-duong-moi-handmade-cao-cap-lipstick-mau-do-cam, https://evagiahan.com/san-pham/son-duong-moi-handmade-cao-cap-lipstick-mau-do-hong, https://evagiahan.com/san-pham/son-duong-moi-handmade-cao-cap-lipstick-mau-do-gach, https://evagiahan.com/san-pham/son-duong-moi-handmade-cao-cap-lipstick-mau-do-dao and https://evagiahan.com/san-pham/son-duong-moi-handmade-cao-cap-lipstick-mau-hong-baby and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://evagiahan.com/danh-muc-san-pham/son-duong-moi-handmade-cao-cap, https://evagiahan.com/san-pham/son-duong-moi-handmade-cao-cap-lipstick-mau-do-cam, https://evagiahan.com/san-pham/son-duong-moi-handmade-cao-cap-lipstick-mau-do-hong, https://evagiahan.com/san-pham/son-duong-moi-handmade-cao-cap-lipstick-mau-do-gach, https://evagiahan.com/san-pham/son-duong-moi-handmade-cao-cap-lipstick-mau-do-dao and https://evagiahan.com/san-pham/son-duong-moi-handmade-cao-cap-lipstick-mau-hong-baby and 6 others took over 3 s to send their HTML from our server.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

3 errors were logged to the browser console while the page loaded, for example “Bootstrap's JavaScript requires jQuery version 1.9.1 or higher, but lower than version 3”.

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

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

Social proof on the homepage: 9 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 4,192 words of visible text.

Before a visitor clicks anything, the page loads Google Ads 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 1 cookie, 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 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.