Website review, no card needed
azia.tech website review
Visit site (opens in a new tab)Reviewed 10 November 202622 issues · 53 checks
This review found 22 issues worth fixing on azia.tech, 6 of them high impact, across 53 checks. The most urgent: page weight: 11.3 MB in 14 requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
84BClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
3.5 MB9 files are served with short cache lifetimes, so returning visitors download them again (3.5 MB).
Improve image delivery
3.3 MB9 images could be 3.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
700 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.
2 third-party services on the page
2 third-party services load with your homepage (Google Fonts and supabase.co), adding 3.0 MB and 0 ms of main-thread time.
supabase.co adds 0 ms
0 mssupabase.co costs a phone 0 ms of main-thread work and 3.0 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Reduce unused JavaScript
133 KiBAbout 133 KiB of JavaScript is downloaded but never used on this page.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 116 ms. During a long task the page ignores taps.
Reduce unused CSS
10 KiBAbout 10 KiB of CSS is downloaded but never applied on this page.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
3 checks passed
Mobile performance score: 95
95/100Your mobile performance score is 95. That is in Google's “good” band (90 and up).
Main-thread work: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 299 ms of it running JavaScript. That is comfortably low.
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 5.1 s
5.1 sVisually, the page fills in at 5.1 s (Speed Index). Good is under 3.4 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
5 checks passed
First Contentful Paint: 1.6 s
1.6 sThe first text or image appears after 1.6 s, inside the 1.8 s “good” threshold.
Time to Interactive: 2.8 s
2.8 sThe page is fully interactive after 2.8 s.
Total Blocking Time: 108 ms
108 msScripts block the page for only 108 ms while loading. Good is under 200 ms.
Largest Contentful Paint: 1.6 s
1.6 sYour largest element renders in 1.6 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “The smart platform for compliance and internal control”.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 11.3 MB in 14 requests
11.3 MBYour homepage downloads 11.3 MB in 14 requests on a phone: media 7.6 MB (1), images 3.5 MB (9) and scripts 226 KiB (1). Under 2 MB keeps phones on slow connections fast.
About 3.2 g of CO₂ per visit
3.20 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.20 g of CO₂e: 384.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
10 buttons without a name
10 buttons have no accessible name, so screen readers announce just “button”.
16 tap targets too small
16 tap targets are too small or too close together to hit reliably with a finger.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No XML sitemap
No XML sitemap at https://azia.tech/sitemap.xml, so Google discovers your pages only by following links.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
4 checks passed
Meta description: 135 characters
Your meta description is 135 characters: “Simplify your compliance operations with AZIA's AI-powered platform. Designed for RCCIs, RCSIs, compliance officers and…”.
Title: 37 characters
Your title is a healthy 37 characters: “AZIA - AI-powered compliance platform”.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place.
AI search readiness
Most text only appears after JavaScript runs
0%A phone browser shows 557 words, but the HTML your server sends has only 0. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://azia.tech/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
1 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Best practices
9 small tap targets
9 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 557 words of copy
The homepage carries about 557 words of visible text.
1 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Learn more about cookies” and “Request a demo”.
Privacy and tracking
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
No consent tool detected
No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at azia.tech, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 22 issues on azia.tech, including 6 speed issues, 5 SEO issues and 4 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.