A · Very good

Page SEO Inspection

https://nzboss.com/
Crawled 12 Nov, 21:43 UTC (17 hr ago)
HTTP 200 135 KB 57 ms TTFB
Download PDF

PDF export is a paid feature

A PDF of the full report, ready to send to a client or a colleague, comes with Basic at $19 a month and every plan above it, along with saved history. The report itself stays free to read.

See the plans
On-Page Checklist 67% Complete
Primary focus: 3 images have no alt attribute, so screen readers announce nothing and engines cannot read them. Fix now →
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.

i 1✓ 150% · fair
Live snippet simulation
Title width: 150px / 580px
N BOSS. nzboss.com
Let's Talk Money

BOSS. offers expert back office support and business solutions to help entrepreneurs thrive while maintaining a healthy work-life balance.

Title tag 150px of 580px

The title is 16 characters. Short titles are fine, but there may be room to say more about what the page offers.

Rendered width

Desktop150px/ 580px
Mobile135px/ 920px

Measured in Arial at the size Google renders result titles, accurate to within a fraction of a percent of a browser. Characters: 16.

Meta description 138 characters

The meta description length is well judged.

Crawling & indexing

Whether search engines can reach, read and index this page at all.

i 1✓ 1694% · excellent
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.nzboss.com/ → 301 → 308 → https://nzboss.com/ (2 redirects)
How to fix
How to fix
Redirect each spelling straight to the final address with a 301 or 308.
HTTP status HTTP 200

The page returns 200 OK.

Redirect chain

The URL resolves without redirects.

Robots directives

No directive prevents indexing.

Canonical tag

The canonical correctly references this page.

https://nzboss.com/
Language

Language is declared as "en-US".

lang="en-US"
hreflang

No hreflang annotations, which is correct for a single-language page.

Viewport

The viewport is configured for mobile.

width=device-width, initial-scale=1
Character encoding

The page declares UTF-8 encoding.

Favicon

A favicon is declared.

Mixed content

All resources load securely.

URL length 19 characters

The URL is 19 characters.

URL readability

The URL is clean and readable.

URL depth 0 levels deep

The page is 0 levels deep.

URL parameters

The URL has no query parameters.

robots.txt 0 KB

robots.txt is present and does not block crawling.

XML sitemap 2 URLs

A sitemap index is published, referencing 2 sitemaps.

Sitemap index referencing 2 sitemaps

Missing pages (404) HTTP 404

A page that does not exist returns HTTP 404, so search engines drop dead addresses.

Content & metadata

What the page says it is about, and how it reads.

! 1i 3✓ 450% · fair
Word count 128 Thin content
Headings 15 Structured
H1 tags 1 Exactly one
Text ratio 0.7% Text vs markup
Heading outline 15 headings
H6 Hello
H1 Welcome
H2 About Us
H3 BOSS.
H3 Solutions
H3 The Team
H3 The Team
H3 Solutions
H3 The Team
H3 Solutions
H3 Solutions
H3 Solutions
H2 2026 Electra Business & Innovation Award FINALIST!
H3 BOSS YOUR BUSINESS
Share image 500 × 500 px

The share image is 500 × 500 pixels. Under 600 × 315, platforms show a small thumbnail beside the link instead of a large card.

https://img1.wsimg.com/isteam/ip/14d5ced3-facc-42bb-acb2-8e2910fdca39/blob-bf19e1b.png
How to fix
How to fix
Use an image of 1200 × 630 pixels.
Twitter card

twitter:card is "summary"; summary_large_image gives a larger preview.

summary
Content length 128 words

The page has roughly 128 words. Fine for a short page such as pricing or contact; a page meant to rank for a topic usually needs more.

How to fix
How to fix
Expand the page to answer the questions a reader arrives with.
Text-to-HTML ratio 0.7% text

Only 0.7% of the page is readable text; the rest is markup and script.

How to fix
How to fix
Move inline scripts and styles to external files, and remove unused markup.
Open Graph tags

Open Graph tags are present.

H1 tag

The page has exactly one h1.

Welcome
Heading hierarchy

The heading outline descends in order.

Table headers

No data tables on this page, so there are no columns to label.

Keyword usage

The page has too little text for keyword analysis to mean anything.

AI & answer readiness

Whether answer engines and AI overviews can extract and trust this page.

i 3✓ 457% · fair
AI crawlers 10/10 All allowed
Readable without JS Yes Served complete
Identity None No structured data
Quotable signals 1/4 Schema, date, author, answers
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
How to fix
Open at least one section with a direct 40 to 60 word answer to the question its heading poses.
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
How to fix
<time datetime="2026-09-17">17 September 2026</time>, or datePublished in Article structured data.
Answer schema

No structured data an answer engine can lift directly, such as FAQPage, HowTo or Article.

How to fix
How to fix
Mark up question-and-answer content as FAQPage, or step-by-step content as HowTo.
Attribution

Attribution signals present: author meta tag, about page, contact page, privacy policy.

author meta tag, about page, contact page

Extractable structure

The page is too short to assess structure.

Entity identity

The page has no structured data, so there is no entity to check.

Readable without JavaScript

The page reads the same with and without JavaScript.

llms.txt for AI agents

llms.txt is published, giving AI agents a curated map of the site.

AI crawler access 10 checked

Every AI crawler checked is allowed to read this page.

Speed & delivery

What makes the page slow, and what the loading experience measures.

! 2✓ 1185% · good
Rendered page
The page as it rendered on a mobile viewport during the performance test
Mobile, measured
The page as it rendered on a desktop viewport
Desktop, measured
LCP Good
0.93s

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.

INP Good
43ms

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.

CLS Good
0

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.

FCP Good
0.93s

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.

TTFBNo data
n/a

Real-user response time

Target ≤ 800ms

Needs real-user data from Chrome UX Report

Render-blocking resources 41 found

41 resources in <head> block the first paint, delaying when anything appears on screen.

script: https://img1.wsimg.com/blobby/go/static/radpack/@widget/LAYOUT/bs-layout14-Theme-publish-Theme-fdc9fc0d.js
script: https://img1.wsimg.com/blobby/go/static/radpack/@widget/MESSAGING/bs-Component-5c8ab323.js
script: https://img1.wsimg.com/blobby/go/static/radpack/@widget/LAYOUT/c/bs-_rollupPluginBabelHelpers-5804ec33.js
script: https://img1.wsimg.com/blobby/go/static/radpack/@widget/LAYOUT/c/bs-defaultSocialIconPack-a2c518b6.js
script: https://img1.wsimg.com/blobby/go/static/radpack/@widget/LAYOUT/c/bs-index-52fbaa26.js
script: https://img1.wsimg.com/blobby/go/static/radpack/@widget/LAYOUT/c/bs-index3-55ad2a27.js
How to fix
How to fix
Add defer to scripts, inline critical CSS, and load the rest asynchronously.
Third-party services 3 services · 534 KB

3 third-party services account for 88% of what this page downloads, 534 KB and 206ms of main-thread time.

Third-party services

Service TransferredMain thread
GoDaddy532 KB199ms
secureserver.net2 KBunder 1ms
reamaze.com1 KB7ms

0.2s of main-thread time

How to fix
How to fix
Audit what each service earns its weight doing, remove any that duplicate another, and load the rest after the page is interactive.
Time to first byte

Time to first byte is 57 ms.

HTML size 135 KB

The HTML document is 20 KB over the wire, compressed from 135 KB of markup.

Deprecated tags

No deprecated HTML tags are used.

Inline styles 21 found

21 inline style attributes.

Compression

The response is compressed with br.

Content-Encoding: br
Page weight 60 requests · 605 KB

The page loads 60 requests totalling 605 KB.

What loaded, by type

Type RequestsTransferred
script47351 KB
font4144 KB
other561 KB
image328 KB
document121 KB

Of these, 58 requests (524 KB) come from third-party domains.

Browser caching 26 KB re-downloaded

Cache lifetimes are long enough that a returning visitor re-downloads only 26 KB.

Short cache lifetimes

FileCache lifetimeSize
img1.wsimg.com/scc-c2.min.js30m22 KB
img1.wsimg.com/tti.min.js30m8 KB
cdn.reamaze.com/reamaze-godaddy-loader.jsnone1 KB

3 expire within the hour

Security

Transport security, reputation and the response headers that protect visitors.

i 6✓ 754% · fair
MIME sniffing

No X-Content-Type-Options header, so browsers may guess a resource type and execute it.

How to fix
How to fix
X-Content-Type-Options: nosniff
Referrer policy

No Referrer-Policy header, so full URLs may leak to third-party sites.

How to fix
How to fix
Referrer-Policy: strict-origin-when-cross-origin
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
How to fix
Permissions-Policy: camera=(), microphone=(), geolocation=()
Cookie flags 1 found

1 of 1 cookie the page sets is missing protective flags.

dps_site_id: no HttpOnly, no SameSite
How to fix
How to fix
Set cookies with Secure; SameSite=Lax, and HttpOnly unless a script genuinely needs to read them.
Version disclosure

Response headers disclose exact software versions, which helps an attacker target known vulnerabilities.

server: DPS/2.0.0+sha-8a831a9
meta generator: Starfield Technologies; Go Daddy Website Builder 8.0.0000
How to fix
How to fix
Suppress version numbers from Server and X-Powered-By, and remove the version from the generator meta tag (in WordPress, a one-line filter or most security plugins).
security.txt

No security.txt, so somebody who finds a vulnerability has no published way to tell you about it.

https://nzboss.com/.well-known/security.txt
How to fix
How to fix
Publish /.well-known/security.txt with a Contact: line (an email address or a form) and an Expires: date.
Email addresses in the page

No email addresses are written into the page for harvesting bots to collect.

HSTS

HTTPS is enforced with Strict-Transport-Security.

max-age=63072000; includeSubDomains; preload
Clickjacking protection

The page is protected against framing.

Content Security Policy

A Content-Security-Policy is set.

TLS certificate 106 days left

The TLS certificate is valid for another 106 days, issued by GoDaddy.com.

106 days remaining
Google Web Risk

Not listed by Google Web Risk for malware, phishing or unwanted software.

TLS version TLS 1.3

Connections use TLS 1.3.

Server & domain

The server and the domain behind the page: protocol, network, registration and email records.

i 3✓ 457% · fair
HTTP/2 HTTP/1.1

Served over HTTP/1.1 only. HTTP/2 loads the page's files in parallel over one connection, and every current browser supports it.

How to fix
How to fix
Turn on HTTP/2 in the web server or the CDN. On most hosts it is a setting, not a change to the site.
IPv6

nzboss.com has no IPv6 address. Visitors on IPv6-only mobile networks reach it through a translation gateway, which adds a step.

How to fix
How to fix
Add an AAAA record. Most hosts and every major CDN provide an IPv6 address.
DMARC policy

nzboss.com 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
How to fix
Publish a TXT record at _dmarc.nzboss.com, starting with v=DMARC1; p=none; rua=mailto:[email protected] to collect reports, then tighten to quarantine or reject.
CDN

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.

Domain expiry 130 days left

nzboss.com is registered until 23 Mar 2027 with GoDaddy.com, LLC.

130 days remaining
Domain age 1 year old

nzboss.com was registered on 23 Mar 2025, 1 year ago. Age is not a ranking factor, but an established name is one buyers and partners look for.

SPF record

nzboss.com publishes an SPF record: v=spf1 include:dc-aa8e722993._spfm.nzboss.com ~all

ads.txt

No ad network loads on this page, so ads.txt is not needed.

Links, media & schema

Links, images and structured data.

! 5i 1✓ 650% · fair
Social share preview From this page's Open Graph tags
Anchor text 6 found

6 links use non-descriptive anchor text, which tells neither readers nor engines where it leads.

Shown as 5 unique destinations; the counts show how often each repeats.

# / lineLink
#1 L902"More" → #<a rel="" role="button" aria-haspopup="menu" data-ux="NavLinkDropdown" data-toggle-ignore="true" id="14519" aria-expanded="false" data-aid="NAV_MORE" data-edit-interactive="true" href="#" data-typography="NavAlpha" class="x-el x-el-a c1-1 c1-2 c1-1g c1-1h c1-1i c1-18 c1-1j c1-19 c1-b c1-1p c1-c c1-…
#2 L902"Find out more" → /solutions<a data-ux-btn="secondary" data-ux="ButtonSecondary" color="HIGHCONTRAST" shape="PILL" fill="GHOST" decoration="NONE" shadow="NONE" data-aid="CTA_BUTTON_RENDERED" href="/solutions" target="" data-tccl="ux2.INTRODUCTION.introduction3.Group.Default.Button.Secondary.14529.click,click" data-page="c1b37…
#3 L902"Learn more" → /solutions ×2<a data-ux-btn="secondary" data-ux="ContentOverlayCardButton" color="HIGHCONTRAST" shape="PILL" fill="GHOST" decoration="NONE" shadow="NONE" data-aid="ABOUT_CTA_BTN_RENDERED0" href="/solutions" target="" data-tccl="ux2.ABOUT.about6.Content.OverlayCard.Button.Secondary.14530.click,click" data-page="…
#4 L902"Learn more" → /about-us<a data-ux-btn="secondary" data-ux="ContentOverlayCardButton" color="HIGHCONTRAST" shape="PILL" fill="GHOST" decoration="NONE" shadow="NONE" data-aid="ABOUT_CTA_BTN_RENDERED1" href="/about-us" target="" data-tccl="ux2.ABOUT.about6.Content.OverlayCard.Button.Secondary.14531.click,click" data-page="e…
#5 L902"Find out more" → https://www.bkh.org.nz/<a rel="noopener" data-ux-btn="primary" data-ux="CardBannerButton" data-aid="CONTENT_CTA_BTN_RENDERED" href="https://www.bkh.org.nz/" target="_blank" data-tccl="ux2.CONTENT.content5.Card.Banner.Button.Primary.14533.click,click" data-typography="ButtonAlpha" class="x-el x-el-a c1-1 c1-2 c1-2i c1-3o …
How to fix
How to fix
Describe the destination: "read our grinder guide" rather than "click here".
Anchor text 3 found

3 links have no anchor text, so its purpose is unreadable without sight of the layout.

Shown as 2 unique destinations; the counts show how often each repeats.

# / lineLink
#1 L902/ ×2<a rel="" role="link" aria-haspopup="menu" data-ux="Link" data-page="287f429b-ed6e-416e-aa2a-319409973b79" title="" href="/" data-typography="LinkAlpha" class="x-el x-el-a c1-1e c1-1f c1-1g c1-1h c1-1i c1-28 c1-1j c1-1l c1-1m c1-1n c1-1o c1-v c1-29 c1-b c1-2a c1-c c1-1q c1-2b c1-1s c1-d c1-e c1-f c…
#2 L902https://www.godaddy.com/websites/website-builder?isc=pwugc&utm_source=wsb&utm_medium=applications&utm_campaign=en-nz_corp_applications_base<a rel="nofollow noopener" role="link" aria-haspopup="true" data-ux="Link" target="_blank" data-aid="FOOTER_POWERED_BY_AIRO_RENDERED_LINK" href="https://www.godaddy.com/websites/website-builder?isc=pwugc&amp;utm_source=wsb&amp;utm_medium=applications&amp;utm_campaign=en-nz_corp_applications_base" d…
How to fix
How to fix
Add link text, or an aria-label where the link is an icon.
Image alt text 3 found

3 images have no alt attribute, so screen readers announce nothing and engines cannot read them.

Shown as 2 unique sources; the counts show how often each repeats.

# / lineImage source
#1 L902//img1.wsimg.com/isteam/ip/14d5ced3-facc-42bb-acb2-8e2910fdca39/blob-bf19e1b.png/:/rs=h:100,cg:true,m/qt=q:95 ×2<img src="//img1.wsimg.com/isteam/ip/14d5ced3-facc-42bb-acb2-8e2910fdca39/blob-bf19e1b.png/:/rs=h:100,cg:true,m/qt=q:95" srcset="//img1.wsimg.com/isteam/ip/14d5ced3-facc-42bb-acb2-8e2910fdca39/blob-bf19e1b.png/:/rs=w:100,h:100,cg:true,m/cr=w:100,h:100/qt=q:95, //img1.wsimg.com/isteam/ip/14d5ced3-fa…
JShttps://img1.wsimg.com/isteam/getty/1441416439/:/<img data-ux="Image" src="https://img1.wsimg.com/isteam/getty/1441416439/:/" data-aid="GALLERY_IMAGE0_RENDERED" class="x-el x-el-img c2-1 c2-2 c2-1p c2-1a c2-1u c2-1v c2-z c2-1w c2-u c2-1x c2-1n c2-1o c2-1y c2-3 c2-4 c2-5 c2-6 c2-7 c2-8">
How to fix
How to fix
<img src="…" alt="What the image shows">, use alt="" only for decorative images.
Image dimensions 3 found

3 images have no width and height, so the page shifts as they load (hurting CLS).

Shown as 2 unique sources; the counts show how often each repeats.

# / lineImage source
#1 L902//img1.wsimg.com/isteam/ip/14d5ced3-facc-42bb-acb2-8e2910fdca39/blob-bf19e1b.png/:/rs=h:100,cg:true,m/qt=q:95 ×2<img src="//img1.wsimg.com/isteam/ip/14d5ced3-facc-42bb-acb2-8e2910fdca39/blob-bf19e1b.png/:/rs=h:100,cg:true,m/qt=q:95" srcset="//img1.wsimg.com/isteam/ip/14d5ced3-facc-42bb-acb2-8e2910fdca39/blob-bf19e1b.png/:/rs=w:100,h:100,cg:true,m/cr=w:100,h:100/qt=q:95, //img1.wsimg.com/isteam/ip/14d5ced3-fa…
JShttps://img1.wsimg.com/isteam/getty/1441416439/:/<img data-ux="Image" src="https://img1.wsimg.com/isteam/getty/1441416439/:/" data-aid="GALLERY_IMAGE0_RENDERED" class="x-el x-el-img c2-1 c2-2 c2-1p c2-1a c2-1u c2-1v c2-z c2-1w c2-u c2-1x c2-1n c2-1o c2-1y c2-3 c2-4 c2-5 c2-6 c2-7 c2-8">
How to fix
How to fix
<img src="…" width="800" height="600">, the browser reserves the space before decoding.
Broken links 7 checked

1 link on this page return an error. Visitors who follow it land on an error page.

403  https://www.godaddy.com/websites/website-builder?isc=pwugc&utm_source=wsb&utm_medium=applications&utm_campaign=en-nz_corp_applications_base
How to fix
How to fix
Update each link to its current destination, or remove it. For a page of your own that moved, add a redirect too.
Structured data

The page has no structured data, so it cannot qualify for rich results.

How to fix
How to fix
<script type="application/ld+json">{"@context":"https://schema.org","@type":"Article","headline":"…"}</script>
Link distribution 24 resources

22 internal and 2 external links.

22 internal, 2 external

22 internal, 2 external

Link rel attributes

Outbound link rel attributes look appropriate.

In-page anchors

In-page anchors resolve to real targets.

Image formats

No heavy legacy image formats found.

Image loading

Image loading strategy looks sound.

Responsive images

Images are served responsively or are small enough not to need it.

What to fix first

Ranked by impact against effort, the top of this list buys the most for the least work.

1
! Recommended 3 images have no alt attribute, so screen readers announce nothing and engines cannot read them.
<img src="…" alt="What the image shows">, use alt="" only for decorative images.
quick fix
2
! Recommended 3 images have no width and height, so the page shifts as they load (hurting CLS).
<img src="…" width="800" height="600">, the browser reserves the space before decoding.
quick fix
3
! Recommended 41 resources in <head> block the first paint, delaying when anything appears on screen.
Add defer to scripts, inline critical CSS, and load the rest asynchronously.
moderate
4
! Recommended 3 third-party services account for 88% of what this page downloads, 534 KB and 206ms of main-thread time.
Audit what each service earns its weight doing, remove any that duplicate another, and load the rest after the page is interactive.
moderate
5
! Recommended 6 links use non-descriptive anchor text, which tells neither readers nor engines where it leads.
Describe the destination: "read our grinder guide" rather than "click here".
quick fix
6
! Recommended 3 links have no anchor text, so its purpose is unreadable without sight of the layout.
Add link text, or an aria-label where the link is an icon.
quick fix
7
! Recommended 1 link on this page return an error. Visitors who follow it land on an error page.
Update each link to its current destination, or remove it. For a page of your own that moved, add a redirect too.
quick fix
8
! Recommended The share image is 500 × 500 pixels. Under 600 × 315, platforms show a small thumbnail beside the link instead of a large card.
Use an image of 1200 × 630 pixels.
quick fix
9
· Notice The page publishes no date. Not expected on a page like this; worth adding if its content goes out of date.
<time datetime="2026-09-17">17 September 2026</time>, or datePublished in Article structured data.
quick fix
10
· Notice The page has no structured data, so it cannot qualify for rich results.
<script type="application/ld+json">{"@context":"https://schema.org","@type":"Article","headline":"…"}</script>
quick fix
11
· Notice No heading is followed by a concise 40 to 60 word answer, the shape featured snippets and AI overviews extract.
Open at least one section with a direct 40 to 60 word answer to the question its heading poses.
moderate
12
· Notice The page has roughly 128 words. Fine for a short page such as pricing or contact; a page meant to rank for a topic usually needs more.
Expand the page to answer the questions a reader arrives with.
involved

Score breakdown

How each area scored. Categories that could not be measured are excluded rather than counted as zero.

Indexability & Crawling38 checks · 10 issues
85
On-Page Content & Structure16 checks · 8 issues
82
Core Web Vitals13 checks · 2 issues
92
Schema & Rich Snippets1 checks · 1 issue
98
Media & Links11 checks · 5 issues
67
Overall scoreGrade A · 53/84 passed
85