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.
Looking for an unbiased news app? Aplomb shows short videos from Reuters, AP, BBC and other vetted newsrooms, and publishes each one's bias…
Looking for an unbiased news app? Aplomb shows short videos from Reuters, AP, BBC and other vetted newsrooms, and publishes each one's bias…
Title width
623px of 580px
The title is about 623px wide and will be truncated in desktop results (limit 580px).
Rendered width
Desktop 623px / 580px Mobile 560px / 920px
Measured in Arial at the size Google renders result titles,
accurate to within a fraction of a percent of a browser. Characters: 62.
How to fix
Rendered width
| Desktop | 623px | / 580px | |
| Mobile | 560px | / 920px |
Measured in Arial at the size Google renders result titles, accurate to within a fraction of a percent of a browser. Characters: 62.
The meta description length is well judged.
Nothing in this section matches the current filter.
Crawling & indexing
Whether search engines can reach, read and index this page at all.
www and https versions
1 found
The other spellings of this address arrive here, but not in one permanent step: a chain costs time on every visit, and a temporary redirect tells search engines the move may not last.
http://www.aplomb.news/ → 308 → 301 → https://aplomb.news/ (2 redirects)
How to fix
The page returns 200 OK.
The URL resolves without redirects.
No directive prevents indexing.
The canonical correctly references this page.
https://aplomb.news/
Language is declared as "en".
lang="en"
3 hreflang annotations declared, including a self-reference.
The viewport is configured for mobile.
width=device-width, initial-scale=1
The page declares UTF-8 encoding.
A favicon is declared.
All resources load securely.
The URL is 20 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 2 sitemaps.
Sitemap index referencing 2 sitemaps
A page that does not exist returns HTTP 404, so search engines drop dead addresses.
Nothing in this section matches the current filter.
Content & metadata
What the page says it is about, and how it reads.
Keyword repetition
"news" makes up 6.0% of the page text, which reads as unnatural repetition rather than writing.
Where these terms appear
Term Count Density
news 43 5.95%
How to fix
Where these terms appear
| Term | Count | Density |
|---|---|---|
| news | 43 | 5.95% |
Open Graph tags are present.
twitter:card is set to summary_large_image.
The page has exactly one h1.
An Unbiased News App, as Close as We Can Make It: Real Journalism in the Format You Already Scroll
The heading outline descends in order.
The page has roughly 1104 words.
Text is 13.6% of the page source.
The table on the page has header cells, so each column is labelled.
The page's prominent terms appear in its title, description or headings.
Where these terms appear
| Term | Count | Density | Title | Description | Headings |
|---|---|---|---|---|---|
| news | 43 | 5.95% | ✓ | ✓ | ✓ |
| aplomb | 27 | 3.73% | ✓ | ✓ | ✓ |
| download | 22 | 3.04% | ✕ | ✕ | ✕ |
| newsrooms | 17 | 2.35% | ✓ | ✓ | ✕ |
| app | 14 | 1.94% | ✓ | ✓ | ✓ |
The page's most frequent terms, from 723 words of content.
What this page is about
Term size reflects how often it appears. Density is not a ranking factor, this is a view of the page's subject, not a target to hit.
The share image loads and is 1200 × 630 pixels, the right size and shape for a large card.
Nothing in this section matches the current filter.
AI & answer readiness
Whether answer engines and AI overviews can extract and trust this page.
Page subject
FAQPage declared without a name or headline.
FAQPage
How to fix
1 heading is followed by a snippet-shaped answer.
The page is dated and about 0 days old.
<time datetime>
Attribution signals present: publisher in structured data, about page, contact page, privacy policy.
publisher in structured data, about page, contact page
Answer-friendly structured data: FAQPage, Question.
FAQPage, Question
2 types: FAQPage, Question
1104 words across 23 headings, 17 lists and 1 tables.
The page names who is behind it: Aplomb.
The page reads the same with and without JavaScript.
llms.txt is published, giving AI agents a curated map of the site.
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
Needs real-user data from Chrome UX Report
Time to first byte is 84 ms.
1 render-blocking resource in the head.
The HTML document is 50 KB.
No deprecated HTML tags are used.
18 inline style attributes.
The response is compressed with br.
Content-Encoding: br
The page loads 14 requests totalling 247 KB.
What loaded, by type
| Type | Requests | Transferred | |
|---|---|---|---|
| image | 7of 8 declared | 132 KB | |
| font | 2 | 87 KB | |
| document | 1 | 11 KB | |
| stylesheet | 1 | 8 KB | |
| script | 2 | 8 KB | |
| other | 1 | 0 KB |
Of these, 0 requests (0 KB) come from third-party domains. The HTML declares 8 images but only 7 loaded, the rest are lazy-loaded and fetched when scrolled to.
Nothing in this section matches the current filter.
Security
Transport security, reputation and the response headers that protect visitors.
Clickjacking protection
Nothing prevents this page being embedded in a frame, which allows clickjacking.
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://aplomb.news/.well-known/security.txt
How to fix
No email addresses are written into the page for harvesting bots to collect.
HTTPS is enforced with Strict-Transport-Security.
max-age=63072000
MIME sniffing is disabled.
Referrer-Policy is "strict-origin-when-cross-origin".
strict-origin-when-cross-origin
The page sets no cookies, so there are none to expose.
No software versions are disclosed in headers or the page.
The TLS certificate is valid for another 64 days, issued by Let's Encrypt.
64 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
aplomb.news 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
The DMARC policy for aplomb.news is p=none, which collects reports but does not stop mail that spoofs the domain.
v=DMARC1; p=none; rua=mailto:[email protected]
How to fix
Served over HTTP/2, which loads a page's files in parallel over one connection.
Served through Vercel, a CDN, so visitors get the page from a server near them.
aplomb.news is registered until 26 Oct 2027 with Name.com, Inc.
339 days remaining
aplomb.news was registered on 26 Oct 2026, under a year ago. Age is not a ranking factor, but an established name is one buyers and partners look for.
aplomb.news publishes an SPF record: v=spf1 include:_spf.google.com ~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.
Image loading
The first image is lazy-loaded. If it is the largest contentful paint element, this directly delays LCP.
<img src="/img/app/30-b11-world-560.webp" loading="lazy">
How to fix
Structured data is valid: Organization, WebSite, MobileApplication, FAQPage.
Organization, WebSite, MobileApplication, FAQPage
4 types: Organization, WebSite, MobileApplication, FAQPage
Eligible for rich results via Organization, FAQPage.
Organization, FAQPage
2 types: Organization, FAQPage
107 internal and 22 external links.
107 internal, 22 external
107 internal, 22 external
Anchor text describes its destinations.
Outbound link rel attributes look appropriate.
In-page anchors resolve to real targets.
All images carry an alt attribute.
All images declare width and height.
No heavy legacy image formats found.
8 already in a modern format
Images are served responsively or are small enough not to need it.
All 25 checked links resolve.
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.