ullikatphoto.com
DOLLY4D ⚙️ Pabrik Angka Toto 4D & Mesin Slot Gacor Dengan Result Harian Super Lengkap
0 failed · 5 warnings · 25 passed
Audited Thu, 16 Jul 2026 10:45:20 GMT · https://ullikatphoto.com/
Meta & Head
22.9/25
Title, description, canonical, social tags — what search engines read first.
Title taghigh impactlow effort
<title> is "DOLLY4D ⚙️ Pabrik Angka Toto 4D & Mesin Slot Gacor Dengan Result Harian Super Lengkap" (85 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.
8 passing checks
- Meta descriptionMeta description is "DOLLY4D menghadirkan pabrik angka Toto 4D dan mesin slot gacor dengan result harian super lengkap, navigasi sederhana, dan akses cepat setiap saat." (147 characters)
- Canonical URLCanonical href is "https://ullikatphoto.com/"
- Viewport meta tagViewport is "width=device-width, initial-scale=1, maximum-scale=1.0, user-scalable=no"
- Character encoding declaredCharacter encoding is declared
- FaviconA <link rel="icon"> is present
- Open Graph tagsAll core Open Graph tags present (og:title, og:description, og:image, og:url)
- Twitter card tagtwitter:card is "product"
- Page allows indexingrobots: INDEX,FOLLOW
Content & Structure
22.1/25
Headings, copy depth, images, structured data, internal linking.
Single H1 headinghigh impactlow effort
2 h1 headings found: "DOLLY4D ⚙️ Pabrik Angka Toto 4D & Mesin Slot Gacor Dengan Result Harian Super Lengkap", "DOLLY4D ⚙️ Pabrik Angka Toto 4D & Mesin Slot Gacor Dengan Result Harian Super Lengkap"
Multiple h1s split the page's main-topic signal, leaving search engines to guess which headline actually defines the page. Keep the one h1 that best states the primary topic and demote the rest to h2 or h3, so the outline reads as a single subject with subtopics. A frequent culprit is a site logo or blog title wrapped in an h1 inside the shared header template — change that to a <div> or <p> and reserve h1 for the page's own content.
Heading hierarchylow impactlow effort
Heading level jumps from h1 ("DOLLY4D ⚙️ Pabrik Angka Toto 4D & Mesin Slot Gacor Dengan Result Harian Super Lengkap") to h3 ("GRATIS ONGKIR")
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.
7 passing checks
- Word count17035 words of visible text
- Image alt text43 of 47 images have alt text
- Structured data (JSON-LD)JSON-LD types found: Organization, WebSite, SiteNavigationElement, BreadcrumbList, WebPage, Article, Service, ItemList, FAQPage
- Hreflang annotations9 valid hreflang link(s) including x-default
- HTML lang attribute<html lang="id">
- JavaScript-dependent contentvisible text ~66410 chars in the initial HTML
- Internal linking44 internal, 67 external links
Technical
23.9/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
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.
HTML5 doctypelow impactlow effort
No doctype declaration found at the start of the document
Without a doctype, browsers render in quirks mode — inconsistent layout, and validators flag the page. Add <!DOCTYPE html> as the very first line of the document, before the <html> tag. Watch out for whitespace, comments, or BOM characters sneaking in before it.
10 passing checks
- Served over HTTPSfinal URL uses https://
- HTTP redirects to HTTPShttp:// redirects to https://
- No mixed content0 http:// subresource references
- Short redirect chainno redirects; URL resolves directly
- robots.txt present and permissiverobots.txt exists and allows crawling
- XML sitemap availablesitemap.xml exists and is valid XML
- Fast time to first byte717 ms
- Reasonable HTML size449.4 KB
- Missing pages return 404missing paths return HTTP 404/410
- www and non-www resolve consistentlywww and non-www converge on the same host
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.