A · Very good

Page SEO Inspection

https://www.aplix.digital/
Crawled 16 Nov, 21:50 UTC (1 day ago)
HTTP 200 23 KB 276 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 76% Complete
Primary focus: The title is about 602px wide and will be truncated in desktop results (limit 580px). 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.

! 1✓ 150% · fair
Live snippet simulation
Title width: 602px / 580px · truncated
A APLIX www.aplix.digital
APLIX | Software Company in Kigali, Rwanda | Creative…

APLIX is a software company in Kigali, Rwanda. We offer creative & branding, technology & development, and data & intelligence. Formerly Issue Six…

Title width 602px of 580px

The title is about 602px wide and will be truncated in desktop results (limit 580px).

Rendered width

Desktop602px/ 580px
Mobile542px/ 920px

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

How to fix
How to fix
Shorten the title so the important words appear first.
Meta description 154 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://aplix.digital/ → 301 → 301 → https://www.aplix.digital/ (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://www.aplix.digital/
Language

Language is declared as "en".

lang="en"
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, viewport-fit=cover
Character encoding

The page declares UTF-8 encoding.

Favicon

A favicon is declared.

Mixed content

All resources load securely.

URL length 26 characters

The URL is 26 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 8 URLs

A sitemap is published, listing 8 URLs.

Lists 8 URLs

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.

✓ 11100% · excellent
Word count 631 Substantive
Headings 19 Structured
H1 tags 1 Exactly one
Text ratio 13.9% Text vs markup
Heading outline 19 headings
H1 WeBuildTheGOAT. — APLIX is a software company in Kigali, Rwanda building digital experien…
H2 Software company: creative technology, UI/UX design & digital products
H3 Primo Pro Services
H3 Decisoria Litis
H3 Misgana SADC
H3 Alfachem Zambia
H3 Farmington Africa
H3 3C Logistics
H3 Mash Ltd
H3 Speed Light Solutions
H2 What we were asked to solve — and what we delivered.
H3 Primo Pro Services
H3 Speed Light Solutions
H3 Creative & Branding
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.

WeBuildTheGOAT. — APLIX is a software company in Kigali, Rwanda building digital experiences, software products and intelligent solutions
Heading hierarchy

The heading outline descends in order.

Content length 631 words

The page has roughly 631 words.

Text-to-HTML ratio 13.9% text

Text is 13.9% 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
digital163.63%✕✕✓
aplix102.27%✓✓✓
data71.59%✕✓✓
services71.59%✕✕✓
com71.59%✓✓✓
Keyword repetition

No term is repeated unnaturally often.

Keyword cloud

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

digitalaplixdataservicescomautomationwebsitecompanyrwandadesignclearcreativetechnologysoftwareexperiencesproductsintelligencebrandcanadastrategybuildworksolutionsorganizationswebprobuiltprofessionalpresencefirmeasyenquiriescrediblefirstimpressionclientsfullquotelogisticslight
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 4✓ 660% · fair
AI crawlers 10/10 All allowed
Readable without JS Yes Served complete
Identity 1/2 Partly declared
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.
Page subject

No structured data describes what this page is about.

Found: ProfessionalService, Organization, WebSite
None of these declare the page's subject.

3 types: ProfessionalService, Organization, WebSite

How to fix
How to fix
Describe the page with the type that fits it, Article for writing, Product for a product, FAQPage for questions and answers. Boilerplate like Organization and BreadcrumbList identifies the site, not the page.
Attribution

Attribution signals present: publisher in structured data, contact page, about page, privacy policy.

publisher in structured data, contact page, about page

Extractable structure 631 words

631 words across 19 headings, 1 lists and 0 tables.

Publisher identity

The page names who is behind it: APLIX.

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.

! 2i 1✓ 975% · 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 Needs work
2.74s

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

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

Third-party services 1 services · 75 KB

1 third-party services account for 62% of what this page downloads, 75 KB and 1ms of main-thread time.

Third-party services

Service TransferredMain thread
Google Fonts75 KBunder 1ms

0.0s 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.
Render-blocking resources 3 found

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

stylesheet: https://fonts.googleapis.com/css2?family=Playfair+Display:wght@500;800;900&family=Montserrat:wght@300;400;500;600;700;800&display=swap
stylesheet: https://fonts.googleapis.com/css2?family=Playfair+Display:wght@500;800;900&family=Montserrat:wght@300;400;500;600;700;800&display=swap
stylesheet: css/style.css
How to fix
How to fix
Add defer to scripts, inline critical CSS, and load the rest asynchronously.
Time to first byte

Time to first byte is 276 ms.

HTML size 23 KB

The HTML document is 23 KB.

Deprecated tags

No deprecated HTML tags are used.

Inline styles 35 found

35 inline style attributes.

Compression

The response is compressed with br.

Content-Encoding: br
Page weight 11 requests · 122 KB

The page loads 11 requests totalling 122 KB.

What loaded, by type

Type RequestsTransferred
font274 KB
image120 KB
stylesheet2of 3 declared12 KB
script59 KB
document16 KB

Of these, 3 requests (75 KB) come from third-party domains.

Security

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

! 1i 6✓ 646% · needs work
Clickjacking protection

Nothing prevents this page being embedded in a frame, which allows clickjacking.

How to fix
How to fix
Content-Security-Policy: frame-ancestors 'self'
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.
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
Content Security Policy

No Content-Security-Policy, the main defence against cross-site scripting.

How to fix
How to fix
Content-Security-Policy: default-src 'self'
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=()
security.txt

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

https://www.aplix.digital/.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
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 75 days left

The TLS certificate is valid for another 75 days, issued by Let's Encrypt.

75 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
IPv6

www.aplix.digital 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.
SPF record

aplix.digital 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
How to fix
Publish a TXT record starting v=spf1 that lists the services that send your mail. A domain that sends none: v=spf1 -all
DMARC policy

aplix.digital 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.aplix.digital, starting with v=DMARC1; p=none; rua=mailto:[email protected] to collect reports, then tighten to quarantine or reject.
HTTP/2 HTTP/2

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

CDN Netlify

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

Domain expiry 350 days left

aplix.digital is registered until 2 Nov 2027 with NameCheap, Inc.

350 days remaining
Domain age Under a year old

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

ads.txt

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

Links, media & schema

Links, images and structured data.

! 1✓ 1192% · excellent
Social share preview From this page's Open Graph tags
Broken links 17 checked

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

403  https://www.linkedin.com/company/aplixdigital/
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

Structured data is valid: ProfessionalService, Organization, WebSite.

ProfessionalService, Organization, WebSite

3 types: ProfessionalService, Organization, WebSite

Rich result eligibility

Eligible for rich results via Organization.

Organization

1 type: Organization

Link distribution 38 resources

19 internal and 19 external links.

19 internal, 19 external

19 internal, 19 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.

What to fix first

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

1
! Recommended The title is about 602px wide and will be truncated in desktop results (limit 580px).
Shorten the title so the important words appear first.
quick fix
2
! Recommended Largest Contentful Paint is 2.7s (lab data), above the 2.5s target.
Optimise the hero image, remove render-blocking CSS and JS, and improve server response time.
moderate
3
! Recommended 1 third-party services account for 62% of what this page downloads, 75 KB and 1ms 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
4
! Recommended Nothing prevents this page being embedded in a frame, which allows clickjacking.
Content-Security-Policy: frame-ancestors 'self'
quick fix
5
! 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
6
· 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
7
· 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
8
· Notice No structured data describes what this page is about.
Describe the page with the type that fits it, Article for writing, Product for a product, FAQPage for questions and answers. Boilerplate like Organization and BreadcrumbList identifies the site, not the page.
quick fix
9
· 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
10
· Notice No X-Content-Type-Options header, so browsers may guess a resource type and execute it.
X-Content-Type-Options: nosniff
quick fix
11
· Notice 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.
Redirect each spelling straight to the final address with a 301 or 308.
quick fix
12
· Notice aplix.digital 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.
Publish a TXT record starting v=spf1 that lists the services that send your mail. A domain that sends none: v=spf1 -all
quick fix

Score breakdown

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

Indexability & Crawling38 checks · 11 issues
80
On-Page Content & Structure22 checks · 5 issues
87
Core Web Vitals12 checks · 3 issues
87
Schema & Rich Snippets2 checks · 0 issues
100
Media & Links10 checks · 1 issue
93
Overall scoreGrade A · 64/86 passed
86