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.
Check any NZ vehicle before you buy with MotorWeb, part of Trade Me. Money owing, stolen and odometer checks, and a $100,000 Repossession…
Check any NZ vehicle before you buy with MotorWeb, part of Trade Me. Money owing, stolen and odometer checks, and a $100,000 Repossession…
The title length is well judged.
Rendered width
| Desktop | 500px | / 580px | |
| Mobile | 450px | / 920px |
Measured in Arial at the size Google renders result titles, accurate to within a fraction of a percent of a browser. Characters: 53.
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
1 other spelling of this address does not lead here, so search engines can treat them as separate pages and split the ranking between them.
http://vir.motorweb.co.nz/pub/ → 301 → https://vir.motorweb.co.nz:443/pub/
How to fix
Redirect chain
2 redirects
The URL redirects 2 times before resolving, costing an extra round trip.
302 https://motorweb.co.nz/
301 https://motorweb.co.nz:443/pub/
200 https://vir.motorweb.co.nz/pub/
How to fix
The page returns 200 OK.
No directive prevents indexing.
The canonical correctly references this page.
https://vir.motorweb.co.nz/pub/
Language is declared as "en-NZ".
lang="en-NZ"
No hreflang annotations, which is correct for a single-language page.
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 31 characters.
The URL is clean and readable.
The page is 1 level deep.
The URL has no query parameters.
robots.txt is present and does not block crawling.
A sitemap is published, listing 33 URLs.
Lists 33 URLs
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.
Open Graph tags are present.
twitter:card is set to summary_large_image.
The page has exactly one h1.
Check the vehicle before you buy.
The heading outline descends in order.
The page has roughly 733 words.
Text is 15.8% of the page source.
No data tables on this page, so there are no columns to label.
The page's prominent terms appear in its title, description or headings.
Where these terms appear
| Term | Count | Density | Title | Description | Headings |
|---|---|---|---|---|---|
| vehicle | 20 | 4.26% | ✓ | ✓ | ✓ |
| report | 11 | 2.34% | ✕ | ✕ | ✓ |
| check | 10 | 2.13% | ✓ | ✓ | ✓ |
| registered | 8 | 1.70% | ✕ | ✕ | ✕ |
| private | 7 | 1.49% | ✕ | ✕ | ✕ |
No term is repeated unnaturally often.
The page's most frequent terms, from 470 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.
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
Page subject
FAQPage declared without a name or headline.
FAQPage
How to fix
Attribution signals present: about page, privacy policy.
about page, privacy policy
Answer-friendly structured data: FAQPage, Question.
FAQPage, Question
2 types: FAQPage, Question
733 words across 15 headings, 11 lists and 0 tables.
The page names who is behind it: MotorWeb.
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
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.
1 render-blocking resource in the head.
The HTML document is 6 KB over the wire, compressed from 30 KB of markup.
No deprecated HTML tags are used.
0 inline style attributes.
The response is compressed with br.
Content-Encoding: br
The page loads 23 requests totalling 472 KB.
What loaded, by type
| Type | Requests | Transferred | |
|---|---|---|---|
| script | 11of 1 declared | 268 KB | |
| image | 5of 11 declared | 91 KB | |
| font | 2 | 69 KB | |
| stylesheet | 1 | 33 KB | |
| document | 1 | 7 KB | |
| other | 3 | 4 KB |
Of these, 0 requests (0 KB) come from third-party domains. The HTML declares 11 images but only 5 loaded, the rest are lazy-loaded and fetched when scrolled to.
Cache lifetimes are long enough that a returning visitor re-downloads only 36 KB.
Short cache lifetimes
| File | Cache lifetime | Size |
|---|---|---|
| vir.motorweb.co.nz/sample-preview-1200.webp | 1d | 54 KB |
| vir.motorweb.co.nz/covered_car_1000.avif | 1d | 16 KB |
| vir.motorweb.co.nz/motorweb-logo-landing.webp | 1d | 15 KB |
| vir.motorweb.co.nz/trademe-by-logo.png | 1d | 4 KB |
| vir.motorweb.co.nz/Sedan_90x48_white.png | 1d | 3 KB |
Nothing in this section matches the current filter.
Security
Transport security, reputation and the response headers that protect visitors.
Email addresses in the page
1 found
1 email address is written into the page as plain text, where harvesting bots collect them for spam and phishing.
[email protected]
How to fix
security.txt
No security.txt, so somebody who finds a vulnerability has no published way to tell you about it.
https://vir.motorweb.co.nz/.well-known/security.txt
How to fix
HTTPS is enforced with Strict-Transport-Security.
max-age=31536000; includeSubDomains
MIME sniffing is disabled.
The page is protected against framing.
Referrer-Policy is "strict-origin-when-cross-origin".
strict-origin-when-cross-origin
A Content-Security-Policy is set.
A Permissions-Policy limits which browser features the page and its embeds can use.
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 89 days, issued by Google Trust Services.
89 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
vir.motorweb.co.nz has no IPv6 address. Visitors on IPv6-only mobile networks reach it through a translation gateway, which adds a step.
How to fix
SPF record
vir.motorweb.co.nz has no SPF record, so nothing tells mail servers who may send email as this domain. Spoofed mail is easier, and genuine mail is likelier to land in spam.
How to fix
DMARC policy
vir.motorweb.co.nz 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.
Announces HTTP/3, which browsers switch to on a later visit for faster connections on poor networks.
Served through Google Cloud CDN, a CDN, so visitors get the page from a server near them.
The registry for .nz does not publish registration dates, so expiry and age are not shown.
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 is valid: WebSite, FAQPage, Product, Organization.
WebSite, FAQPage, Product, Organization
4 types: WebSite, FAQPage, Product, Organization
Eligible for rich results via FAQPage, Product, Organization.
FAQPage, Product, Organization
3 types: FAQPage, Product, Organization
46 internal and 1 external links.
46 internal, 1 external
46 internal, 1 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.
3 already in a modern format
Image loading strategy looks sound.
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.