everon.com website review

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

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

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

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

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

Your mobile performance score is 57 (desktop: 73). Pages that score under 90 lose visitors before the first paint.

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

74 KiB could be saved by minifying JavaScript.

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

4 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Google Analytics and others), adding 208 KiB and 211 ms of main-thread time.

15 KiB could be saved by minifying CSS.

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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 46.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “SLEEP MASTER”.

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

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

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

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

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

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

13 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-17, real Chrome visitors' tap response (inp) went from 97 ms to 94 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 24.6 MB in 127 requests on a phone: images 23.8 MB (93), scripts 578 KiB (18) and stylesheets 147 KiB (6). Under 2 MB keeps phones on slow connections fast.

13 images weigh 20.0 MB together. On a phone connection a single image that size takes seconds.

13 images are downloaded at several times the size a phone draws them, for example hoa-tiet.png at 1,108 px wide, shown at 280 px. Resized copies would save about 9.4 MB.

40 images (22.3 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.

10 images further down the page (15.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

uu-dai-chan-ga-11.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).

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

Certain ARIA roles must be contained by particular parents: 5 elements on the page fail this check, rated critical by axe-core.

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

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

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

ARIA role should be appropriate for the element: 5 elements on the page fail this check, rated minor by axe-core.

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

Your title is only 16 characters: “Everon Trang chủ”. 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.

Your meta description is only 22 characters: “Trang thông tin everon”. 70 to 160 characters is enough to sell the click.

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

No XML sitemap at https://everon.com/sitemap.xml, so Google discovers your pages only by following links.

1 link has no real href, so search engines can't follow it.

Your <h1> is empty.

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

The homepage links to 244 pages on everon.com and 8 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 /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.

/bo-suu-tap/bst-nhung-manh-em, /san-pham/citrus-eptmc27022, /san-pham/beech-epc27027 and /san-pham/gingham-bpc702 took over 3 s to send their HTML from our server.

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

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

4 images are served at too low a resolution for sharp phone screens.

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.

everon.com 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.

everon.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust 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 426 words of visible text.

everon.com has no DMARC record, so nothing tells receivers what to do with mail that fails SPF or DKIM. Gmail and Yahoo require DMARC from bulk senders.

We found no DKIM key on the selectors the big email providers use. If you send through one of them, turning on DKIM signing improves delivery.

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 and Google Tag Manager (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 5 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 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.