beritasingkawangg.com
Berita Singkawang - Portal Berita Terkini Kota Singkawang
1 failed · 5 warnings · 22 passed
Audited Mon, 13 Jul 2026 08:45:53 GMT · https://beritasingkawangg.com/
Meta & Head
22.2/25
Title, description, canonical, social tags — what search engines read first.
Meta descriptionhigh impactlow effort
Meta description is "Berita Singkawang menyajikan informasi terbaru seputar Kota Singkawang, Kalimantan Barat, meliputi politik, ekonomi, wisata, budaya, olahraga, pendidikan, dan peristiwa terkini." (177 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.
Faviconlow impactlow effort
No <link rel="icon"> and /favicon.ico does not respond
Google displays favicons beside mobile search results, and browsers show them in tabs, bookmarks, and history — a missing icon makes your listing look generic and less trustworthy next to competitors. Create an icon of at least 48x48 pixels, serve it at /favicon.ico, and reference it with <link rel="icon" href="/favicon.png" type="image/png"> in <head>. Make sure robots.txt doesn't block the icon's path — search engines must be able to crawl it to display it.
7 passing checks
- Title tag<title> is "Berita Singkawang - Portal Berita Terkini Kota Singkawang" (57 characters)
- Canonical URLCanonical href is "https://beritasingkawangg.com/"
- Viewport meta tagViewport is "width=device-width, initial-scale=1.0"
- Character encoding declaredCharacter encoding is declared
- Open Graph tagsAll core Open Graph tags present (og:title, og:description, og:image, og:url)
- Twitter card tagtwitter:card is "summary_large_image"
- Page allows indexingrobots: index, follow
Content & Structure
17/25
Headings, copy depth, images, structured data, internal linking.
Word counthigh impactlow effort
163 words of visible text
Under 300 words, search engines typically classify a page as thin content, and thin pages rarely rank for anything competitive. Decide which query this page should answer, then write substantive copy — aim for 600+ words covering what it is, how it works, common questions, and concrete examples. If the page genuinely has nothing more to say, merge it into a stronger related page with a 301 redirect rather than padding it with filler that helps no one.
Single H1 headinghigh impactlow effort
2 h1 headings found: "Berita Singkawang", "Portal Berita Singkawang Terpercaya"
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.
5 passing checks
- Heading hierarchy5 headings in order without skipped levels
- Structured data (JSON-LD)JSON-LD types found: WebSite
- HTML lang attribute<html lang="id">
- JavaScript-dependent contentvisible text ~1287 chars in the initial HTML
- Internal linking6 internal, 0 external links
Technical
23.3/25
HTTPS, redirects, robots, sitemap, speed, crawlability.
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.
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
- Fast time to first byte424 ms
- Reasonable HTML size3.6 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.