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.
APLIX is a software company in Kigali, Rwanda. We offer creative & branding, technology & development, and data & intelligence. Formerly Issue Six…
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
Desktop 602px / 580px Mobile 542px / 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
Rendered width
| Desktop | 602px | / 580px | |
| Mobile | 542px | / 920px |
Measured in Arial at the size Google renders result titles, accurate to within a fraction of a percent of a browser. Characters: 64.
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://aplix.digital/ → 301 → 301 → https://www.aplix.digital/ (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.aplix.digital/
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, viewport-fit=cover
The page declares UTF-8 encoding.
A favicon is declared.
All resources load securely.
The URL is 26 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 is published, listing 8 URLs.
Lists 8 URLs
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.
Open Graph tags are present.
twitter:card is set to summary_large_image.
The page has exactly one h1.
WeBuildTheGOAT. — APLIX is a software company in Kigali, Rwanda building digital experiences, software products and intelligent solutions
The heading outline descends in order.
The page has roughly 631 words.
Text is 13.9% of the page source.
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 |
|---|---|---|---|---|---|
| digital | 16 | 3.63% | ✕ | ✕ | ✓ |
| aplix | 10 | 2.27% | ✓ | ✓ | ✓ |
| data | 7 | 1.59% | ✕ | ✓ | ✓ |
| services | 7 | 1.59% | ✕ | ✕ | ✓ |
| com | 7 | 1.59% | ✓ | ✓ | ✓ |
No term is repeated unnaturally often.
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.
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.
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
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
Attribution signals present: publisher in structured data, contact page, about page, privacy policy.
publisher in structured data, contact page, about page
631 words across 19 headings, 1 lists and 0 tables.
The page names who is behind it: APLIX.
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
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 Transferred Main thread
Google Fonts 75 KB under 1ms
0.0s of main-thread time
How to fix
Third-party services
| Service | Transferred | Main thread | |
|---|---|---|---|
| Google Fonts | 75 KB | under 1ms |
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
Time to first byte is 276 ms.
The HTML document is 23 KB.
No deprecated HTML tags are used.
35 inline style attributes.
The response is compressed with br.
Content-Encoding: br
The page loads 11 requests totalling 122 KB.
What loaded, by type
| Type | Requests | Transferred | |
|---|---|---|---|
| font | 2 | 74 KB | |
| image | 1 | 20 KB | |
| stylesheet | 2of 3 declared | 12 KB | |
| script | 5 | 9 KB | |
| document | 1 | 6 KB |
Of these, 3 requests (75 KB) come from third-party domains.
Nothing in this section matches the current filter.
Security
Transport security, reputation and the response headers that protect visitors.
Clickjacking protection
Nothing prevents this page being embedded in a frame, which allows clickjacking.
How to fix
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
MIME sniffing
No X-Content-Type-Options header, so browsers may guess a resource type and execute it.
How to fix
Referrer policy
No Referrer-Policy header, so full URLs may leak to third-party sites.
How to fix
Content Security Policy
No Content-Security-Policy, the main defence against cross-site scripting.
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
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
HTTPS is enforced with Strict-Transport-Security.
max-age=31536000
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 75 days, issued by Let's Encrypt.
75 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.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
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
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
Served over HTTP/2, which loads a page's files in parallel over one connection.
Served through Netlify, a CDN, so visitors get the page from a server near them.
aplix.digital is registered until 2 Nov 2027 with NameCheap, Inc.
350 days remaining
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.
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.
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
Structured data is valid: ProfessionalService, Organization, WebSite.
ProfessionalService, Organization, WebSite
3 types: ProfessionalService, Organization, WebSite
Eligible for rich results via Organization.
Organization
1 type: Organization
19 internal and 19 external links.
19 internal, 19 external
19 internal, 19 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.
All images declare width and height.
No heavy legacy image formats found.
Image loading strategy looks sound.
Images are served responsively or are small enough not to need it.
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.