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.
Sydney AI & Digital consultancy for small to medium projects your big agency overcharges for. Two founders, a fixed price and a live date before we start.
Sydney AI & Digital consultancy for small to medium projects your big agency overcharges for. Two founders, a fixed price and a live date before we start.
The title length is well judged.
Rendered width
| Desktop | 523px | / 580px | |
| Mobile | 470px | / 920px |
Measured in Arial at the size Google renders result titles, accurate to within a fraction of a percent of a browser. Characters: 59.
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://hiaitus.ai/ → 308 → 308 → https://www.hiaitus.ai/ (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://www.hiaitus.ai
Language is declared as "en".
lang="en"
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 23 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 4 sitemaps.
Sitemap index referencing 4 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.
Text-to-HTML ratio
3.3% text
Only 3.3% of the page is readable text; the rest is markup and script.
How to fix
Open Graph tags are present.
twitter:card is set to summary_large_image.
The page has exactly one h1.
AI that earns its place in your business
The heading outline descends in order.
The page has roughly 821 words.
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 |
|---|---|---|---|---|---|
| agency | 8 | 1.57% | ✕ | ✓ | ✓ |
| medium | 7 | 1.38% | ✕ | ✓ | ✓ |
| business | 7 | 1.38% | ✕ | ✕ | ✓ |
| weeks | 6 | 1.18% | ✕ | ✕ | ✓ |
| small | 6 | 1.18% | ✕ | ✓ | ✓ |
No term is repeated unnaturally often.
The page's most frequent terms, from 509 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.
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
Publisher identity
No structured data names the publisher or author.
3 entity type(s) found, none naming a publisher:
ProfessionalService, WebSite, FAQPage
3 types: ProfessionalService, WebSite, FAQPage
How to fix
Page subject
FAQPage declared without a name or headline.
FAQPage
How to fix
1 heading is followed by a snippet-shaped answer.
Attribution signals present: publisher in structured data, about page, contact page.
publisher in structured data, about page, contact page
Answer-friendly structured data: FAQPage, Question.
FAQPage, Question
2 types: FAQPage, Question
821 words across 31 headings, 9 lists and 0 tables.
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
Render-blocking resources
14 found
14 resources in <head> block the first paint, delaying when anything appears on screen.
stylesheet: /_next/static/immutable/chunks/30kjhtcbz8ds0.css
stylesheet: /_next/static/immutable/chunks/0p7sc8qre6ssj.css
stylesheet: /_next/static/immutable/chunks/2p6c5x2v8k4zf.css
stylesheet: /_next/static/immutable/chunks/3_2gslqhstf9q.css
script: /_next/static/immutable/chunks/0c0hxoamwjsbw.js
script: /ingest/static/exception-autocapture.js?v=1.399.2
How to fix
HTML size
149 KB
The HTML document is 149 KB, heavier than about 90% of pages.
How to fix
Time to first byte is 382 ms.
No deprecated HTML tags are used.
19 inline style attributes.
The response is compressed with br.
Content-Encoding: br
The page loads 41 requests totalling 770 KB.
What loaded, by type
| Type | Requests | Transferred | |
|---|---|---|---|
| script | 22of 29 declared | 536 KB | |
| font | 2 | 90 KB | |
| image | 6 | 69 KB | |
| other | 6 | 27 KB | |
| stylesheet | 4 | 25 KB | |
| document | 1 | 23 KB |
Of these, 1 requests (29 KB) come from third-party domains.
1 third-party service load on this page, adding 29 KB.
Third-party services
| Service | Transferred | Main thread | |
|---|---|---|---|
| mux.com | 29 KB | under 1ms |
Cache lifetimes are long enough that a returning visitor re-downloads only 74 KB.
Short cache lifetimes
| File | Cache lifetime | Size |
|---|---|---|
| www.hiaitus.ai/surveys.js | 5m | 49 KB |
| image.mux.com/thumbnail.webp | 7d | 29 KB |
| www.hiaitus.ai/image | 1m | 9 KB |
| www.hiaitus.ai/exception-autocapture.js | 5m | 8 KB |
| www.hiaitus.ai/image | 1m | 4 KB |
| www.hiaitus.ai/image | 1m | 3 KB |
| www.hiaitus.ai/config.js | 5m | 2 KB |
6 expire within the hour
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
Content Security Policy
The Content-Security-Policy allows unsafe-inline or unsafe-eval, which undermines much of its protection.
default-src 'self'; base-uri 'self'; object-src 'none'; frame-ancestors 'self'; form-action 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe…
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.hiaitus.ai/.well-known/security.txt
How to fix
HTTPS is enforced with Strict-Transport-Security.
max-age=63072000; 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 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 82 days, issued by Let's Encrypt.
82 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
www.hiaitus.ai has no IPv6 address. Visitors on IPv6-only mobile networks reach it through a translation gateway, which adds a step.
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.
hiaitus.ai is registered until 11 Apr 2027 with GoDaddy.com, LLC.
150 days remaining
hiaitus.ai was registered on 11 Apr 2025, 1 year ago. Age is not a ranking factor, but an established name is one buyers and partners look for.
hiaitus.ai publishes an SPF record: v=spf1 include:_spf.google.com ~all
hiaitus.ai has a DMARC policy of reject.
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
1 found
1 image has no width and height, so the page shifts as they load (hurting CLS).
# / line Image source #1 L22 /api/media/file/checkedit-square-transparent-1.png<img src="/api/media/file/checkedit-square-transparent-1.png" alt="Checked It" class="size-full object-contain">
How to fix
| # / line | Image source |
|---|---|
| #1 L22 | /api/media/file/checkedit-square-transparent-1.png<img src="/api/media/file/checkedit-square-transparent-1.png" alt="Checked It" class="size-full object-contain"> |
Structured data is valid: ProfessionalService, WebSite, FAQPage.
ProfessionalService, WebSite, FAQPage
3 types: ProfessionalService, WebSite, FAQPage
Eligible for rich results via FAQPage.
FAQPage
1 type: FAQPage
40 internal and 3 external links.
40 internal, 3 external
40 internal, 3 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.
No heavy legacy image formats found.
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.