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.
No meta description, Google will generate a snippet from the page.
No meta description, Google will generate a snippet from the page.
Meta description
The page has no meta description, so search engines will improvise the snippet.
How to fix
The title is 4 characters. Short titles are fine, but there may be room to say more about what the page offers.
Rendered width
| Desktop | 53px | / 580px | |
| Mobile | 48px | / 920px |
Measured in Arial at the size Google renders result titles, accurate to within a fraction of a percent of a browser. Characters: 4.
Nothing in this section matches the current filter.
Crawling & indexing
Whether search engines can reach, read and index this page at all.
Canonical tag
No canonical tag, so duplicate URLs may compete with each other.
How to fix
robots.txt
No robots.txt was found. Crawlers will request it on every visit and receive an error.
How to fix
XML sitemap
No sitemap was found at /sitemap.xml, and robots.txt does not declare one.
https://www.ledgerpro.co.nz/sitemap.xml
How to fix
The page returns 200 OK.
The URL resolves without redirects.
No directive prevents indexing.
Language is declared as "en-US".
lang="en-US"
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 28 characters.
The URL is clean and readable.
The page is 0 levels deep.
The URL has no query parameters.
A page that does not exist returns HTTP 404, so search engines drop dead addresses.
All 3 other spellings of this address redirect here in one permanent step.
Nothing in this section matches the current filter.
Content & metadata
What the page says it is about, and how it reads.
This page has no headings.
H1 tag
The page has no h1, so its main subject is undeclared.
How to fix
Content length
39 words
The page has roughly 39 words, too little for search engines to tell what it is about.
How to fix
Share image
64 × 64 px
The share image is 64 × 64 pixels. Under 600 × 315, platforms show a small thumbnail beside the link instead of a large card.
https://lh7-us.googleusercontent.com/sitesv-images-rt/APXyLQd1MQyQ8khSRHQMcV3KzTfD_dE_spaklGx7DIhOzHNdoADxHzR0Z9VyxzQNCKejdd6w9Sz6iFH_TRSexzQ7m_SXHdv2kDokOIYJvokzNvpjkb7LFBglXLCxfV7U4GezYgze59uNLFSYeoxewZa1D40n_g9B-ZMx-qGLt6xfRWDX-f_i5kqjcBdqHpC5=w16383
How to fix
Open Graph tags
Open Graph tags are incomplete: og:description missing.
Open Graph tags
Tag Status
og:title ✓ Present og:description ✕ Missing og:image ✓ Present og:url ✓ Present og:type ✓ Present
How to fix
Open Graph tags
| Tag | Status | |
|---|---|---|
| og:title | ✓ | Present |
| og:description | ✕ | Missing |
| og:image | ✓ | Present |
| og:url | ✓ | Present |
| og:type | ✓ | Present |
Twitter card
No twitter:card tag, so shared links render as a small preview.
How to fix
Text-to-HTML ratio
0.3% text
Only 0.3% of the page is readable text; the rest is markup and script.
How to fix
No data tables on this page, so there are no columns to label.
The page has too little text for keyword analysis to mean anything.
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
Answer schema
No structured data an answer engine can lift directly, such as FAQPage, HowTo or Article.
How to fix
llms.txt for AI agents
No llms.txt. AI coding agents have no curated map of this site.
https://www.ledgerpro.co.nz/llms.txt returned nothing
How to fix
Attribution signals present: about page, contact page.
about page, contact page
The page is too short to assess structure.
The page has no structured data, so there is no entity to check.
The page reads the same with and without JavaScript.
No robots.txt, so no AI crawler is excluded by one.
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
Third-party services
5 services · 1.7 MB
5 third-party services account for 98% of what this page downloads, 1.7 MB and 530ms of main-thread time.
Third-party services
Service Transferred Main thread
Google CDN 1.1 MB 410ms googleusercontent.com 240 KB 18ms Google Fonts 190 KB 2ms Other Google APIs/SDKs 171 KB 101ms google.com 2 KB under 1ms
0.5s of main-thread time
How to fix
Third-party services
| Service | Transferred | Main thread | |
|---|---|---|---|
| Google CDN | 1.1 MB | 410ms | |
| googleusercontent.com | 240 KB | 18ms | |
| Google Fonts | 190 KB | 2ms | |
| Other Google APIs/SDKs | 171 KB | 101ms | |
| google.com | 2 KB | under 1ms |
Browser caching
120 KB re-downloaded
3 files have cache lifetimes short enough that returning visitors download 120 KB again.
Short cache lifetimes
File Cache lifetime Size
lh7-us.googleusercontent.com/…ie9jIjqDE9Ux8x3Jwn3xqNvezIMOmUcKg=w16383 1d 209 KB www.gstatic.com/lazy.min.js 50m 41 KB lh7-us.googleusercontent.com/…B-ZMx-qGLt6xfRWDX-f_i5kqjcBdqHpC5=w16383 1d 8 KB
1 expire within the hour
How to fix
Short cache lifetimes
| File | Cache lifetime | Size |
|---|---|---|
| lh7-us.googleusercontent.com/…ie9jIjqDE9Ux8x3Jwn3xqNvezIMOmUcKg=w16383 | 1d | 209 KB |
| www.gstatic.com/lazy.min.js | 50m | 41 KB |
| lh7-us.googleusercontent.com/…B-ZMx-qGLt6xfRWDX-f_i5kqjcBdqHpC5=w16383 | 1d | 8 KB |
Render-blocking resources
4 found
4 resources in <head> block the first paint, delaying when anything appears on screen.
stylesheet: https://fonts.googleapis.com/css?family=Oswald%3A400%2C600%2C700%7COpen%20Sans%3A400%2C600%2C700&display=swap
stylesheet: https://fonts.googleapis.com/css?family=Google+Sans:400,500|Roboto:300,400,500,700|Source+Code+Pro:400,700&display=swap
stylesheet: https://www.gstatic.com/_/atari/_/ss/k=atari.vw.jluZxktbEcI.L.W.O/am=AAAAAAwAAQ/d=1/rs=AGEqA5m1eUhZqz4_uQfTjKtlNrCGdSFUnQ
script: https://apis.google.com/js/client.js?onload=gapiLoaded
How to fix
Time to first byte is 159 ms.
The HTML document is 139 KB.
No deprecated HTML tags are used.
46 inline style attributes.
The response is compressed with gzip.
Content-Encoding: gzip
The page loads 37 requests totalling 1.7 MB.
What loaded, by type
| Type | Requests | Transferred | |
|---|---|---|---|
| script | 14of 5 declared | 1.1 MB | |
| stylesheet | 4of 3 declared | 226 KB | |
| image | 2 | 217 KB | |
| font | 6 | 181 KB | |
| document | 4 | 63 KB | |
| other | 7 | 9 KB |
Of these, 35 requests (1.7 MB) come from third-party domains.
Nothing in this section matches the current filter.
Security
Transport security, reputation and the response headers that protect visitors.
HSTS
No Strict-Transport-Security header, so a first visit over HTTP can be intercepted before the redirect.
How to fix
Content Security Policy
The Content-Security-Policy allows unsafe-inline or unsafe-eval, which undermines much of its protection.
base-uri 'self';object-src 'none';report-uri /_/view/cspreport;script-src 'report-sample' 'nonce-l6i4rnjFyHitOi8k6xkmvA' 'unsafe-inline' 'unsafe-eval';worker-s…
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
TLS version
The server still accepts TLS 1.0 or 1.1, retired in 2021. No current browser uses them, so they serve only very old clients and attackers forcing a weaker connection.
How to fix
security.txt
No security.txt, so somebody who finds a vulnerability has no published way to tell you about it.
https://www.ledgerpro.co.nz/.well-known/security.txt
How to fix
No email addresses are written into the page for harvesting bots to collect.
MIME sniffing is disabled.
The page is protected against framing.
Referrer-Policy is "origin".
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 34 days, issued by Google Trust Services.
34 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.
SPF record
ledgerpro.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
Served over HTTP/2, which loads a page's files in parallel over one connection.
No CDN was detected in the response, so every visitor is served from the origin server. Fine for a local audience; a CDN helps a distant one.
The registry for .nz does not publish registration dates, so expiry and age are not shown.
www.ledgerpro.co.nz has an IPv6 address, so IPv6-only networks reach it directly.
ledgerpro.co.nz has a DMARC policy of quarantine.
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 dimensions
2 found
2 images have no width and height, so the page shifts as they load (hurting CLS).
All 2 point at the same source, one template reused down the page.
# / line Image source
#1 L106 https://lh7-us.googleusercontent.com/sitesv-images-rt/APXyLQd1MQyQ8khSRHQMcV3KzTfD_dE_spaklGx7DIhOzHNdoADxHzR0Z9VyxzQNCKejdd6w9Sz6iFH_TRSexzQ7m_SXHdv2kDokOIYJvokzNvpjkb7LFBglXLCxfV7U4GezYgze59uNLFSYeoxewZa1D40n_g9B-ZMx-qGLt6xfRWDX-f_i5kqjcBdqHpC5=w16383 ×2<img src="https://lh7-us.googleusercontent.com/sitesv-images-rt/APXyLQd1MQyQ8khSRHQMcV3KzTfD_dE_spaklGx7DIhOzHNdoADxHzR0Z9VyxzQNCKejdd6w9Sz6iFH_TRSexzQ7m_SXHdv2kDokOIYJvokzNvpjkb7LFBglXLCxfV7U4GezYgze59uNLFSYeoxewZa1D40n_g9B-ZMx-qGLt6xfRWDX-f_i5kqjcBdqHpC5=w16383" class="r9CsCb" role="img" aria-lab…
How to fix
All 2 point at the same source, one template reused down the page.
| # / line | Image source |
|---|---|
| #1 L106 | https://lh7-us.googleusercontent.com/sitesv-images-rt/APXyLQd1MQyQ8khSRHQMcV3KzTfD_dE_spaklGx7DIhOzHNdoADxHzR0Z9VyxzQNCKejdd6w9Sz6iFH_TRSexzQ7m_SXHdv2kDokOIYJvokzNvpjkb7LFBglXLCxfV7U4GezYgze59uNLFSYeoxewZa1D40n_g9B-ZMx-qGLt6xfRWDX-f_i5kqjcBdqHpC5=w16383 ×2<img src="https://lh7-us.googleusercontent.com/sitesv-images-rt/APXyLQd1MQyQ8khSRHQMcV3KzTfD_dE_spaklGx7DIhOzHNdoADxHzR0Z9VyxzQNCKejdd6w9Sz6iFH_TRSexzQ7m_SXHdv2kDokOIYJvokzNvpjkb7LFBglXLCxfV7U4GezYgze59uNLFSYeoxewZa1D40n_g9B-ZMx-qGLt6xfRWDX-f_i5kqjcBdqHpC5=w16383" class="r9CsCb" role="img" aria-lab… |
Structured data is present as Microdata or RDFa. JSON-LD is Google's preferred format.
32 internal and 0 external links.
32 internal, 0 external
32 internal, 0 external
Anchor text describes its destinations.
Outbound link rel attributes look appropriate.
In-page anchors resolve to real targets.
Every image has an accessible name or is marked decorative (0 via alt, 2 via aria-label, 0 decorative).
No heavy legacy image formats found.
Image loading strategy looks sound.
Images are served responsively or are small enough not to need it.
All 10 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.