No checks match that filter.
Full diagnostics
Every check that ran, grouped by what it affects. Problems appear first in each group.
Meta Tags & Search Snippet Simulator
The tags that decide how this page is titled and described in search results.
No meta description, Google will generate a snippet from the page.
No meta description, Google will generate a snippet from the page.
Title tag
The page has no title tag.
How to fix
Meta description
The page has no meta description, so search engines will improvise the snippet.
How to fix
Nothing in this section matches the current filter.
Crawling & indexing
Whether search engines can reach, read and index this page at all.
Robots directives
"noindex" is set via meta robots, so this page will not appear in search results.
meta robots: noindex, nofollow
How to fix
Robots directives
"nofollow" is set via meta robots.
meta robots: noindex, nofollow
How to fix
Canonical tag
No canonical tag, so duplicate URLs may compete with each other.
How to fix
Language
The html element has no lang attribute, which affects both search targeting and screen readers.
How to fix
Viewport
The viewport does not set width=device-width, so the layout may not adapt to the device.
initial-scale=1.0
How to fix
Character encoding
No character encoding is declared, so browsers must guess and may render text incorrectly.
How to fix
Missing pages (404)
HTTP 200
A page that does not exist returns HTTP 200. Search engines can index endless empty pages, and Search Console reports them as soft 404s.
https://www.laysvietnam.com/wrp-missing-1904212784 answered HTTP 200
How to fix
Favicon
No favicon is declared. Google shows one beside your result on mobile.
How to fix
The page returns 200 OK.
The URL resolves without redirects.
No hreflang annotations, which is correct for a single-language page.
All resources load securely.
The URL is 28 characters.
The URL is clean and readable.
The page is 0 levels deep.
The URL has no query parameters.
robots.txt is present and does not block crawling.
A sitemap index is published, referencing 7 sitemaps.
Sitemap index referencing 7 sitemaps
All 3 other spellings of this address redirect here in one permanent step.
Nothing in this section matches the current filter.
Content & metadata
What the page says it is about, and how it reads.
This page has no headings.
H1 tag
The page has no h1, so its main subject is undeclared.
How to fix
Content length
6 words
The page has roughly 6 words, too little for search engines to tell what it is about.
How to fix
Open Graph tags
Open Graph tags are incomplete: og:title, og:description, og:image missing.
Open Graph tags
Tag Status
og:title ✕ Missing og:description ✕ Missing og:image ✕ Missing og:url ✓ Present og:type ✓ Present
How to fix
Open Graph tags
| Tag | Status | |
|---|---|---|
| og:title | ✕ | Missing |
| og:description | ✕ | Missing |
| og:image | ✕ | Missing |
| og:url | ✓ | Present |
| og:type | ✓ | Present |
Twitter card
No twitter:card tag, so shared links render as a small preview.
How to fix
Text is 9.0% of the page source.
No data tables on this page, so there are no columns to label.
The page has too little text for keyword analysis to mean anything.
Nothing in this section matches the current filter.
AI & answer readiness
Whether answer engines and AI overviews can extract and trust this page.
Answer readiness
0 found
No heading is followed by a concise 40 to 60 word answer, the shape featured snippets and AI overviews extract.
How to fix
Content freshness
The page publishes no date. Not expected on a page like this; worth adding if its content goes out of date.
How to fix
Attribution
Nothing on the page identifies who is behind it: no author, publisher, or about and contact links.
How to fix
Answer schema
No structured data an answer engine can lift directly, such as FAQPage, HowTo or Article.
How to fix
llms.txt for AI agents
No llms.txt. AI coding agents have no curated map of this site.
https://www.laysvietnam.com/llms.txt returned nothing
How to fix
The page is too short to assess structure.
The page has no structured data, so there is no entity to check.
The page reads the same with and without JavaScript.
Every AI crawler checked is allowed to read this page.
Nothing in this section matches the current filter.
Speed & delivery
What makes the page slow, and what the loading experience measures.
Largest Contentful Paint
Target ≤ 2.5s
What this measures
How long until the largest thing on screen, usually the hero image, video or headline block, has finished rendering. It is a proxy for "when did this page feel loaded".
What moves it: Serve the hero image in a modern format at the size it is displayed, preload it, and remove render-blocking CSS and JavaScript ahead of it. A slow server response delays it too, so check TTFB first.
Interaction to Next Paint
Target ≤ 200ms
What this measures
How long the page takes to respond visibly after a tap, click or key press, measured across every interaction, not just the first. High INP is what makes a page feel unresponsive even once it looks ready.
What moves it: Break up long JavaScript tasks so the main thread is free to respond, defer work that is not needed for the interaction, and avoid large re-renders on every event.
Cumulative Layout Shift
Target ≤ 0.1
What this measures
How much visible content jumps around while the page loads. This is what makes someone tap the wrong thing because a banner or image pushed the layout down underneath their finger.
What moves it: Give images and video explicit width and height so the browser reserves the space, reserve room for ads and embeds, and avoid inserting content above what is already on screen.
First Contentful Paint
Target ≤ 1.8s
What this measures
How long until anything at all appears, the first text or image painted. It separates "the page starts slowly" from "the biggest element is slow": a fast FCP with a slow LCP points at the hero, while both slow points at the server.
What moves it: Cut render-blocking CSS and JavaScript in the head, inline the styles needed for the first screen, and improve the server response time.
Real-user response time
Target ≤ 800ms
What this measures
How long real visitors waited for the first byte of the response, the 75th percentile across everyone who actually loaded the page, not a single test from one location.
What moves it: Cache the response at the edge, host closer to your visitors, and reduce the work done before the first byte is sent, database queries, template rendering and third-party calls.
Compression
The HTML is served uncompressed. Gzip or Brotli typically cuts it by 70%.
How to fix
Browser caching
151 KB re-downloaded
2 files have cache lifetimes short enough that returning visitors download 151 KB again.
Short cache lifetimes
File Cache lifetime Size
img.youtube.com/maxresdefault.jpg 2h 152 KB www.laysvietnam.com/Lays_Logo_Large_AE_RGB_Master.png.webp none 37 KB
1 expire within the hour
How to fix
Short cache lifetimes
| File | Cache lifetime | Size |
|---|---|---|
| img.youtube.com/maxresdefault.jpg | 2h | 152 KB |
| www.laysvietnam.com/Lays_Logo_Large_AE_RGB_Master.png.webp | none | 37 KB |
1 render-blocking resource in the head.
The HTML document is 0 KB.
No deprecated HTML tags are used.
2 inline style attributes.
The page loads 54 requests totalling 2.0 MB.
What loaded, by type
| Type | Requests | Transferred | |
|---|---|---|---|
| image | 8of 0 declared | 854 KB | |
| script | 20of 1 declared | 757 KB | |
| font | 6 | 271 KB | |
| stylesheet | 13of 0 declared | 111 KB | |
| document | 1 | 36 KB | |
| other | 2 | 1 KB | |
| media | 4 | 0 KB |
Of these, 4 requests (442 KB) come from third-party domains.
3 third-party services load on this page, adding 442 KB.
Third-party services
| Service | Transferred | Main thread | |
|---|---|---|---|
| Google Tag Manager | 289 KB | 174ms | |
| YouTube | 152 KB | under 1ms | |
| Google Analytics | 1 KB | under 1ms |
0.2s of main-thread time
Nothing in this section matches the current filter.
Security
Transport security, reputation and the response headers that protect visitors.
HSTS
No Strict-Transport-Security header, so a first visit over HTTP can be intercepted before the redirect.
How to fix
Clickjacking protection
Nothing prevents this page being embedded in a frame, which allows clickjacking.
How to fix
Cookie flags
2 found
2 of 2 cookies the page sets are missing protective flags. Without Secure a cookie can be sent over plain http, where anybody on the network can read it.
visid_incap_3283800: no Secure, no SameSite
incap_ses_159_3283800: no Secure, no HttpOnly, no SameSite
How to fix
MIME sniffing
No X-Content-Type-Options header, so browsers may guess a resource type and execute it.
How to fix
Referrer policy
No Referrer-Policy header, so full URLs may leak to third-party sites.
How to fix
Content Security Policy
No Content-Security-Policy, the main defence against cross-site scripting.
How to fix
Permissions policy
No Permissions-Policy header, so any script or embed on the page may ask for the camera, microphone or location.
How to fix
security.txt
No security.txt, so somebody who finds a vulnerability has no published way to tell you about it.
https://www.laysvietnam.com/.well-known/security.txt
How to fix
No email addresses are written into the page for harvesting bots to collect.
No software versions are disclosed in headers or the page.
The TLS certificate is valid for another 195 days, issued by DigiCert Inc.
195 days remaining
Not listed by Google Web Risk for malware, phishing or unwanted software.
Connections use TLS 1.3.
Nothing in this section matches the current filter.
Server & domain
The server and the domain behind the page: protocol, network, registration and email records.
IPv6
www.laysvietnam.com has no IPv6 address. Visitors on IPv6-only mobile networks reach it through a translation gateway, which adds a step.
How to fix
DMARC policy
laysvietnam.com has no DMARC record, so mail servers have no instruction for mail that fails SPF or DKIM. Gmail and Yahoo require one from bulk senders.
How to fix
Served over HTTP/2, which loads a page's files in parallel over one connection.
Served through Imperva, a CDN, so visitors get the page from a server near them.
laysvietnam.com is registered until 15 Nov 2030 with MAT BAO CORPORATION.
1457 days remaining
laysvietnam.com was registered on 15 Nov 2018, 8 years ago. Age is not a ranking factor, but an established name is one buyers and partners look for.
laysvietnam.com publishes an SPF record: v=spf1 mx include:103.138.88.18 -all
No ad network loads on this page, so ads.txt is not needed.
Nothing in this section matches the current filter.
Links, media & schema
Links, images and structured data.
Structured data
The page has no structured data, so it cannot qualify for rich results.
How to fix
The page contains no links.
The page contains no images.
No links were available to check.
Nothing in this section matches the current filter.
What to fix first
Ranked by impact against effort, the top of this list buys the most for the least work.
Score breakdown
How each area scored. Categories that could not be measured are excluded rather than counted as zero.