johnjernigan.me
LINK ĐĂNG KÝ EV99 Oksub - TRANG CHỦ EV99.COM ĐĂNG NHẬP EV 99 UY TÍN T7/2026
0 failed · 9 warnings · 21 passed
Audited Sun, 19 Jul 2026 07:15:20 GMT · https://johnjernigan.me/
Meta & Head
19.4/25
Title, description, canonical, social tags — what search engines read first.
Title taghigh impactlow effort
<title> is "LINK ĐĂNG KÝ EV99 Oksub - TRANG CHỦ EV99.COM ĐĂNG NHẬP EV 99 UY TÍN T7/2026" (75 characters)
Search engines truncate titles past roughly 60 characters and often rewrite very short or vague ones, so the message you wrote may never actually be shown. Rewrite the title to 30–60 characters that lead with the primary keyword and end with your brand, e.g. "Merge PDF Files Online Free | YourBrand". Front-load the important words, since truncation always cuts from the end. Don't pad a short title with repeated keywords just to hit the range — clarity wins clicks, not length.
Meta descriptionhigh impactlow effort
Meta description is "EV99 là nhà cái trực tuyến uy tín đang nổi đình đám hiện nay, cung cấp kho trò chơi đa dạng như bóng đá, lô đề, xổ số và casino trực tuyến,... tất cả đều được ..." (162 characters)
Search engines truncate descriptions past roughly 160 characters, and very short ones waste the snippet space that persuades searchers to pick your listing over the next one. Rewrite it to 70–160 characters: state what the page offers, work the primary keyword in naturally (matching words get bolded in results), and end with a benefit or call to action. Don't cram in keywords — the description influences clicks, not rankings, so write it for humans.
Open Graph tagsmedium impactlow effort
Missing Open Graph tags: og:url
Your Open Graph markup is incomplete, so social platforms fall back to guessed text or drop the preview image entirely when this page is shared — a broken card gets far fewer clicks than a complete one. Add the missing og:url tag to <head>. For og:image, use an absolute https:// URL to an image around 1200x630 pixels; relative paths are the usual reason previews break. Re-check with a platform's sharing debugger afterwards, since preview cards are cached.
6 passing checks
- Canonical URLCanonical href is "https://johnjernigan.me/vi-vn/"
- Viewport meta tagViewport is "width=device-width, initial-scale=1"
- Character encoding declaredCharacter encoding is declared
- FaviconA <link rel="icon"> is present
- Twitter card tagtwitter:card is "summary_large_image"
- Page allows indexingrobots: follow, index, max-snippet:-1, max-video-preview:-1, max-image-preview:large
Content & Structure
23.5/25
Headings, copy depth, images, structured data, internal linking.
Heading hierarchylow impactlow effort
Heading level jumps from h2 ("Tin tức mới nhất của EV99") to h5 ("Top 5 sai lầm khi chơi tại EV88 khiến bạn mất tiền oan")
Headings form the page's outline; when levels jump (h2 straight to h4), search engines and screen readers get a broken table of contents and the relationship between sections turns ambiguous. Fix the jump by stepping down one level at a time — promote the deeper heading, or add the missing intermediate level. The usual cause is choosing heading tags for their default font size; set sizes in CSS instead and let the tags reflect actual document structure.
Hreflang annotationslow impactlow effort
2 hreflang link(s) present but no x-default entry
Your hreflang set has no x-default entry, so search engines must guess which version to show visitors whose language you don't list — and they often pick a poorly matched one. Add <link rel="alternate" hreflang="x-default" href="https://www.example.com/"> pointing at your fallback page, typically the English version or a language-selector page. Remember that hreflang must be reciprocal: every version, including the x-default target, should carry the full set of alternate links back to all the others.
7 passing checks
- Single H1 heading1 h1 found: "EV99 LINK ĐĂNG KÝ EV99 Johnjernigan | TRANG CHỦ EV99.COM ĐĂNG NHẬP EV 99 UY TÍN T7/2026"
- Word count4526 words of visible text
- Image alt text24 of 24 images have alt text
- Structured data (JSON-LD)JSON-LD types found: Place, Casino, Organization, WebSite, ImageObject, AboutPage, Person, Article, Person, Casino
- HTML lang attribute<html lang="vi">
- JavaScript-dependent contentvisible text ~17082 chars in the initial HTML
- Internal linking59 internal, 14 external links
Technical
20.5/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
Fast time to first bytehigh impactmedium effort
1437 ms
Time to first byte is the floor under every other speed metric — the browser can't parse, render, or fetch anything until the first byte arrives, so a slow TTFB drags down all Core Web Vitals and tests crawlers' patience. Add caching in front of the origin: full-page caching at a CDN (Cloudflare, Fastly) helps most, followed by server-side caches (Redis, object caching) and indexes on slow database queries. Measure from locations near your actual users — tuning only your fastest region leaves distant visitors just as slow.
Short redirect chainmedium impactlow effort
https://portaldanilovgrad.me/ (301) → https://johnjernigan.me/
Every redirect hop adds a round-trip before the visitor sees anything, each hop can leak a little link equity, and crawlers abandon long chains — which can leave the destination page undiscovered. Trace the chain above and point the first URL directly at the final destination in a single 301; commonly this means merging separate http-to-https and non-www-to-www rules into one combined redirect. Also update internal links to reference the final URL directly, so most visitors never enter the chain at all.
XML sitemap availablemedium impactlow effort
no sitemap.xml found
Without an XML sitemap, search engines discover pages only by following links, so new, deep, or weakly linked pages get found slowly or not at all. Generate one at /sitemap.xml — most frameworks and CMSs have a generator built in or as a plugin — listing every canonical, indexable URL, then add "Sitemap: https://www.example.com/sitemap.xml" to robots.txt and submit it in Google Search Console. Keep it clean: listing redirected, noindexed, or 404 URLs erodes crawler trust in the whole file.
Response compression enabledlow impactlow effort
no content-encoding header
This HTML is served uncompressed, so every visitor downloads far more bytes than necessary — text compresses extremely well, and the savings directly speed up first render on slow connections. Enable Brotli or gzip on your server or CDN: in nginx it's "gzip on;" (or the brotli module), in Apache it's mod_deflate via .htaccess, and on most CDNs it's a single toggle. Make sure compression covers all text types (HTML, CSS, JS, JSON, SVG), but skip already-compressed images — recompressing them wastes CPU for no gain.
8 passing checks
- Served over HTTPSfinal URL uses https://
- HTTP redirects to HTTPShttp:// redirects to https://
- No mixed content0 http:// subresource references
- robots.txt present and permissiverobots.txt exists and allows crawling
- Reasonable HTML size108.1 KB
- Missing pages return 404missing paths return HTTP 404/410
- www and non-www resolve consistentlywww and non-www converge on the same host
- HTML5 doctype<!DOCTYPE html> present
Performance
Core Web Vitals scoring via Google PageSpeed is coming soon.
Share your score
Embed this live badge on your site — it updates whenever the audit is re-run.