A · Very good

Page SEO Inspection

https://solidstateid.com/
Crawled 17 Nov, 03:17 UTC (22 hr ago)
HTTP 200 59 KB 212 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 86% Complete
Primary focus: 2 other spellings of this address do not lead here, so search engines can treat them as separate pages and split the ranking between 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.

✓ 2100% · excellent
Live snippet simulation
Title width: 514px / 580px
S SolidState ID solidstateid.com
Jasa Jaringan & Infrastruktur IT Samarinda | SolidState ID

Jasa jaringan komputer dan infrastruktur IT di Samarinda untuk UMKM dan kantor. Melayani LAN, Wi-Fi, MikroTik, VPN, Starlink, server, NAS, dan…

Title tag 514px of 580px

The title length is well judged.

Rendered width

Desktop514px/ 580px
Mobile462px/ 920px

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

Meta description 155 characters

The meta description length is well judged.

Crawling & indexing

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

! 1✓ 1694% · excellent
www and https versions 2 found

2 other spellings of this address do not lead here, so search engines can treat them as separate pages and split the ranking between them.

http://solidstateid.com/ answers HTTP 200 itself
http://www.solidstateid.com/ answers HTTP 522 itself
How to fix
How to fix
Redirect every spelling (http and https, with and without www) to https://solidstateid.com/ with a single 301.
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://solidstateid.com/
Language

Language is declared as "id".

lang="id"
hreflang

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

Viewport

The viewport is configured for mobile.

width=device-width
Character encoding

The page declares UTF-8 encoding.

Favicon

A favicon is declared.

Mixed content

All resources load securely.

URL length 25 characters

The URL is 25 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 2 KB

robots.txt is present and does not block crawling.

XML sitemap 1 URLs

A sitemap index is published, referencing 1 sitemaps.

Sitemap index referencing 1 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.

! 1✓ 1091% · excellent
Word count 1,502 Substantive
Headings 62 Structured
H1 tags 1 Exactly one
Text ratio 19.0% Text vs markup
Heading outline 62 headings
H1 Jaringan stabil untuk operasional bisnis yang tidak boleh terhenti.
H2 Internet cepat belum tentu jaringan internalnya sehat.
H3 Wi-Fi lambat atau tidak merata
H3 Kasir, printer, atau CCTV sering terputus
H3 Internet cadangan tidak berpindah otomatis
H3 Jaringan tidak memiliki dokumentasi
H2 Cari akar masalah sebelum membeli perangkat baru.
H3 Scope dasar
H2 Hasil pekerjaan diserahkan sesuai ruang lingkup yang disepakati.
H3 Ringkasan hasil pemeriksaan
H3 Diagram dan catatan konfigurasi
H3 Checklist pengujian dan serah terima
H2 Jaringan kantor dan usaha
H3 Network Health Check
Keyword repetition

"dan" makes up 5.3% of the page text, which reads as unnatural repetition rather than writing.

Where these terms appear

TermCountDensity
dan745.28%
How to fix
How to fix
Rewrite so the term appears where it reads naturally. Search engines match meaning, not repetition.
Open Graph tags

Open Graph tags are present.

Twitter card

twitter:card is set to summary_large_image.

H1 tag

The page has exactly one h1.

Jaringan stabil untuk operasional bisnis yang tidak boleh terhenti.
Heading hierarchy

The heading outline descends in order.

Content length 1,502 words

The page has roughly 1502 words.

Text-to-HTML ratio 19.0% text

Text is 19.0% of the page source.

Table headers

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

Keyword placement

The page's prominent terms appear in its title, description or headings.

Where these terms appear

TermCountDensityTitleDescriptionHeadings
dan745.28%✕✓✓
jaringan362.57%✓✓✓
yang292.07%✕✕✓
perangkat211.50%✕✕✓
mulai171.21%✕✕✓
Keyword cloud

The page's most frequent terms, from 1402 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.

danjaringanyangperangkatmulaiuntukkonfigurasisertanetworkkamisistematausebelumlayananpekerjaanpointsamarindatidakdarijasaoperasionalroutermasalahlebihsolidstateutamabackupwebsiteaplikasihealthpemeriksaandapatproyekbiayamembantulanlihatdokumentasidatakapasitas
Share image 1200 × 630 px

The share image loads and is 1200 × 630 pixels, the right size and shape for a large card.

AI & answer readiness

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

i 3✓ 770% · good
AI crawlers 10/10 All allowed
Readable without JS Yes Served complete
Identity 1/2 Partly declared
Quotable signals 2/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.
Page subject

FAQPage declared without a name or headline.

FAQPage
How to fix
How to fix
Give each of these a name, or a headline for an Article. The type says what kind of thing the page is about; without a name it does not say which thing.
Attribution

Attribution signals present: publisher in structured data, author meta tag.

publisher in structured data, author meta tag

Answer schema

Answer-friendly structured data: FAQPage, Question.

FAQPage, Question

2 types: FAQPage, Question

Extractable structure 1,502 words

1502 words across 62 headings, 3 lists and 0 tables.

Publisher identity

The page names who is behind it: SolidState ID.

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.

i 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.91s

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
0ms

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.91s

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 3 found

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

stylesheet: /_astro/BaseLayout.BEde8KvQ.css
stylesheet: /_astro/index.DyCjLT8W.css
stylesheet: /_astro/home.BRitQqav.css
How to fix
How to fix
Add defer to scripts, inline critical CSS, and load the rest asynchronously.
Inline styles 52 found

52 elements carry inline style attributes, which cannot be cached and inflate the document.

How to fix
How to fix
Move repeated styles into a cacheable stylesheet.
Time to first byte

Time to first byte is 212 ms.

HTML size 59 KB

The HTML document is 59 KB.

Deprecated tags

No deprecated HTML tags are used.

Compression

The response is compressed with zstd.

Content-Encoding: zstd
Page weight 7 requests · 49 KB

The page loads 7 requests totalling 49 KB.

What loaded, by type

Type RequestsTransferred
document116 KB
stylesheet312 KB
script110 KB
image1of 4 declared9 KB
other11 KB

Of these, 1 requests (10 KB) come from third-party domains. The HTML declares 4 images but only 1 loaded, the rest are lazy-loaded and fetched when scrolled to.

Third-party services 1 services · 10 KB

1 third-party service load on this page, adding 10 KB.

Third-party services

Service TransferredMain thread
Cloudflare10 KB10ms

0.0s of main-thread time

Browser caching 4 KB re-downloaded

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

Short cache lifetimes

FileCache lifetimeSize
static.cloudflareinsights.com/…823e78c4301a35b7e07294d873017920888140921d10 KB

Security

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

i 4✓ 1071% · good
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
How to fix
Use a contact form, or show the address through a script or as an image. If the address must stay, give it a strong spam filter.
Content Security Policy

The Content-Security-Policy allows unsafe-inline or unsafe-eval, which undermines much of its protection.

default-src 'self'; img-src 'self' data: https:; style-src 'self' 'unsafe-inline'; script-src 'self' 'unsafe-inline' https://static.cloudflareinsights.com http…
How to fix
How to fix
Use nonces or hashes instead of unsafe-inline.
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
How to fix
Disable TLS 1.0 and 1.1 and keep 1.2 and 1.3. On a CDN this is usually a "minimum TLS version" setting.
security.txt

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

https://solidstateid.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.
HSTS

HTTPS is enforced with Strict-Transport-Security.

max-age=31536000; includeSubDomains; preload
MIME sniffing

MIME sniffing is disabled.

Clickjacking protection

The page is protected against framing.

Referrer policy

Referrer-Policy is "strict-origin-when-cross-origin".

strict-origin-when-cross-origin
Permissions policy

A Permissions-Policy limits which browser features the page and its embeds can use.

Cookie flags

The page sets no cookies, so there are none to expose.

Version disclosure

No software versions are disclosed in headers or the page.

TLS certificate 42 days left

The TLS certificate is valid for another 42 days, issued by Google Trust Services.

42 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 1✓ 788% · good
DMARC policy

The DMARC policy for solidstateid.com is p=none, which collects reports but does not stop mail that spoofs the domain.

v=DMARC1; p=none; rua=mailto:[email protected]; ruf=mailto:[email protected]; sp=none; adkim=r; aspf=r
How to fix
How to fix
Once the reports show only your own services sending, move to p=quarantine and then p=reject.
HTTP/2 HTTP/2

Served over HTTP/2, which loads a page's files in parallel over one connection.

HTTP/3 HTTP/3

Announces HTTP/3, which browsers switch to on a later visit for faster connections on poor networks.

CDN Cloudflare

Served through Cloudflare, a CDN, so visitors get the page from a server near them.

Domain expiry 227 days left

solidstateid.com is registered until 2 Jul 2027 with Web Commerce Communications Limited dba WebNic.cc.

227 days remaining
Domain age Under a year old

solidstateid.com was registered on 2 Jul 2026, under a year ago. Age is not a ranking factor, but an established name is one buyers and partners look for.

IPv6

solidstateid.com has an IPv6 address, so IPv6-only networks reach it directly.

SPF record

solidstateid.com publishes an SPF record: v=spf1 include:zohomail.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.

✓ 12100% · excellent
Social share preview From this page's Open Graph tags
Structured data

Structured data is valid: Organization, LocalBusiness, WebSite, FAQPage.

Organization, LocalBusiness, WebSite, FAQPage

4 types: Organization, LocalBusiness, WebSite, FAQPage

Rich result eligibility

Eligible for rich results via Organization, LocalBusiness, FAQPage.

Organization, LocalBusiness, FAQPage

3 types: Organization, LocalBusiness, FAQPage

Link distribution 63 resources

52 internal and 11 external links.

52 internal, 11 external

52 internal, 11 external

Anchor text

Anchor text describes its destinations.

Link rel attributes

Outbound link rel attributes look appropriate.

In-page anchors

In-page anchors resolve to real targets.

Image alt text

All images carry an alt attribute.

Image dimensions

All images declare width and height.

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.

Broken links 25 checked

All 25 checked links resolve.

What to fix first

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

1
! Recommended 2 other spellings of this address do not lead here, so search engines can treat them as separate pages and split the ranking between them.
Redirect every spelling (http and https, with and without www) to https://solidstateid.com/ with a single 301.
quick fix
2
! Recommended "dan" makes up 5.3% of the page text, which reads as unnatural repetition rather than writing.
Rewrite so the term appears where it reads naturally. Search engines match meaning, not repetition.
moderate
3
· Notice 3 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
· Notice FAQPage declared without a name or headline.
Give each of these a name, or a headline for an Article. The type says what kind of thing the page is about; without a name it does not say which thing.
quick fix
5
· 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
6
· 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
7
· Notice 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.
Disable TLS 1.0 and 1.1 and keep 1.2 and 1.3. On a CDN this is usually a "minimum TLS version" setting.
quick fix
8
· Notice No security.txt, so somebody who finds a vulnerability has no published way to tell you about it.
Publish /.well-known/security.txt with a Contact: line (an email address or a form) and an Expires: date.
quick fix
9
· Notice 1 email address is written into the page as plain text, where harvesting bots collect them for spam and phishing.
Use a contact form, or show the address through a script or as an image. If the address must stay, give it a strong spam filter.
quick fix
10
· Notice The DMARC policy for solidstateid.com is p=none, which collects reports but does not stop mail that spoofs the domain.
Once the reports show only your own services sending, move to p=quarantine and then p=reject.
quick fix
11
· Notice 52 elements carry inline style attributes, which cannot be cached and inflate the document.
Move repeated styles into a cacheable stylesheet.
involved
12
· Notice The Content-Security-Policy allows unsafe-inline or unsafe-eval, which undermines much of its protection.
Use nonces or hashes instead of unsafe-inline.
involved

Score breakdown

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

Indexability & Crawling40 checks · 6 issues
86
On-Page Content & Structure22 checks · 4 issues
91
Core Web Vitals13 checks · 2 issues
97
Schema & Rich Snippets2 checks · 0 issues
100
Media & Links10 checks · 0 issues
100
Overall scoreGrade A · 75/89 passed
92