Website review, no card needed
insa.gov.et website review
Visit site (opens in a new tab)Reviewed 17 November 202647 issues · 89 checks
This review found 47 issues worth fixing on insa.gov.et, 21 of them high impact, across 89 checks. The most urgent: improve image delivery. 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
70C- #97,425 of 116,487 reviewed websitesbeats 14%
- #60,058 of 66,776 online storesbeats 8%
- #2,040 of 2,670 WooCommerce storesbeats 19%
Closest competitors among WooCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 3.8 s |
| Jun 20, 2026 | 4.6 s |
| Jul 4, 2026 | 4.7 s |
| Jul 11, 2026 | 4.4 s |
| Jul 18, 2026 | 3.8 s |
| Aug 8, 2026 | 4.1 s |
| Aug 15, 2026 | 4.5 s |
| Aug 22, 2026 | 4.6 s |
| Aug 29, 2026 | 5.1 s |
| Sep 5, 2026 | 4.1 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 4.3 s |
| Oct 10, 2026 | 3.8 s |
| Oct 17, 2026 | 3.5 s |
| Nov 14, 2026 | 4.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jul 4, 2026 | 253 ms |
| Aug 15, 2026 | 155 ms |
| Aug 22, 2026 | 146 ms |
| Aug 29, 2026 | 127 ms |
| Sep 5, 2026 | 160 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Improve image delivery
3.6 s · 3.5 MB19 images could be 3.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.6 s faster on a phone.
Render-blocking requests
4.4 s20 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.4 s.
Font display
2.3 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 2.3 s).
Reduce unused CSS
1.4 s · 282 KiBAbout 282 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.4 s faster on a phone.
Mobile performance score: 45
45/100Your mobile performance score is 45. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Use efficient cache lifetimes
6.6 MB1 file is served with short cache lifetimes, so returning visitors download them again (6.6 MB).
Main-thread work: 2.6 s
A phone's processor spends 2.6 s on main-thread work while loading, 388 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Minify CSS
150 ms · 28 KiB28 KiB could be saved by minifying CSS.
3 third-party services on the page
3 third-party services load with your homepage (jQuery CDN, JSDelivr CDN and Google Fonts), adding 199 KiB and 113 ms of main-thread time.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 120 ms. During a long task the page ignores taps.
Reduce unused JavaScript
24 KiBAbout 24 KiB of JavaScript is downloaded but never used 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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify JavaScript
4 KiB4 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 226 ms
226 msYour server sent the HTML in 226 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 4.1 s
4.1 sReal visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.8 s
3.8 sReal visitors see the first content after 3.8 s (75th percentile). Good is under 1.8 s.
Largest Contentful Paint: 14.2 s
14.2 sYour largest element takes 14.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Information Network Security Administration”. Most of its time is element render delay (8.1 s).
Speed Index: 15.7 s
15.7 sVisually, the page fills in at 15.7 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 14.6 s
14.6 sThe page becomes fully interactive after 14.6 s. Good is under 3.8 s.
First Contentful Paint: 4.3 s
4.3 sThe first text or image appears after 4.3 s on a phone. Good is under 1.8 s.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.244
0.244The layout shifts by 0.244 while loading, so content jumps under the reader's thumb. Good is under 0.1.
31 images without width and height
31 images have no width and height attributes, so the layout jumps as each one loads.
4 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Tap response (INP) got 30% faster for real visitors
-30%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 253 ms to 160 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 3.8 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 50 ms
50 msScripts block the page for only 50 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 14.5 MB in 85 requests
14.5 MBYour homepage downloads 14.5 MB in 85 requests on a phone: media 6.6 MB (1), images 6.1 MB (32) and fonts 1.3 MB (12). Under 2 MB keeps phones on slow connections fast.
15 images far larger than shown
2.5 MB15 images are downloaded at several times the size a phone draws them, for example 1786608601130910221.jpg at 1,080 px wide, shown at 342 px. Resized copies would save about 2.5 MB.
1 image over 500 KB
1786608601130910221.jpg weighs 611 KiB. On a phone connection a single image that size takes seconds.
16 images in older formats
16 images (3.6 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.
15 images below the first screen load straight away
15 images further down the page (3.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.1 g of CO₂ per visit
4.11 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.11 g of CO₂e: 493.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
15 text elements with low contrast
15 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
6 images without alt text
6 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (16 elements)
All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.
No main landmark
The page has no <main> landmark, so screen-reader users cannot jump straight to the content.
17 links without text
17 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 49 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“Information Network Security Administration” and “INSA”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No robots.txt
There is no robots.txt at insa.gov.et/robots.txt, the first file search crawlers ask for.
10 links with vague text
10 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
60 internal links, 25 external
The homepage links to 60 pages on insa.gov.et and 25 external pages.
2 checks passed
Title: 50 characters
Your title is a healthy 50 characters: “INSA | Information Network Security Administration”.
XML sitemap found
Your XML sitemap is reachable at https://insa.gov.et/sitemap.xml.
AI search readiness
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.
2 checks passed
AI answer engines may read the site
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (748 words), so crawlers that don't run JavaScript still read it.
Other pages
1 linked page is broken
Your homepage links to https://insa.gov.et/insaRequest, which answers with an error. Visitors hit a dead end and search engines drop it.
15 pages share a title
/, https://insa.gov.et/changelanguage/en, https://insa.gov.et/changelanguage/amh, https://insa.gov.et/about, https://insa.gov.et/service and https://insa.gov.et/product and 9 others all use the title “INSA | Information Network Security Administration”. Search engines can't tell which page to show for a search, so each competes with the others.
6 pages without a meta description
https://insa.gov.et/changelanguage/en, https://insa.gov.et/changelanguage/amh, https://insa.gov.et/documentations, https://insa.gov.et/service/Digital-Forensic-Service, https://insa.gov.et/service/Cloud-Seeding and https://insa.gov.et/service/Fraud-Prevention-Service have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages share a meta description
https://insa.gov.et/about, https://insa.gov.et/service, https://insa.gov.et/product, https://insa.gov.et/blog, https://insa.gov.et/package and https://insa.gov.et/secureyoursystem and 2 others use the same meta description. A description written for each page earns more clicks.
7 pages without an H1
https://insa.gov.et/service, https://insa.gov.et/product, https://insa.gov.et/contact, https://insa.gov.et/gate-a-quote, https://insa.gov.et/service/Digital-Forensic-Service and https://insa.gov.et/service/Cloud-Seeding and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.
7 pages slow to respond
https://insa.gov.et/changelanguage/en, https://insa.gov.et/changelanguage/amh, https://insa.gov.et/about, https://insa.gov.et/service, https://insa.gov.et/documentations and https://insa.gov.et/package and 1 other took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 28 found) and read each the way a search engine does.
3 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 14 pages that loaded have a <title>.
Best practices
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://insa.gov.et/assets/front/css/dynamic-css.php?color=0C59DB&gcolor1=1FA2FF&gcolor2=C…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
2 checks passed
Tap targets are thumb-sized
31 of 36 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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 714 words of copy
The homepage carries about 714 words of visible text.
6 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “[email protected]” and “INSA Request”.
13 calls to action
The homepage has 13 calls to action, for example “[email protected]”, “INSA Request” and “Request Cyber Audit”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block, 9 customer or partner logos and 1 trust badge.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
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.
4 other companies contacted
Loading the homepage contacts 4 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 insa.gov.et, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2025.
Stack
- CMS
- WordPress
- Framework
- jQuery
- E-commerce
- WooCommerce
- Hosting
- Ethionet
Company
- Founded
- 2006
- Headquarters
- Addis Ababa
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on insa.gov.et, including 17 speed issues, 7 SEO issues and 2 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.