Website review, no card needed
nagico.com website review
Visit site (opens in a new tab)Reviewed 30 October 202623 issues · 57 checks
This review found 23 issues worth fixing on nagico.com, 8 of them high impact, across 57 checks. The most urgent: fails Core Web Vitals for real visitors. Google's speed test didn't respond, so speed is not measured here; your full playbook measures it. 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
Not scored yet: Google's speed test didn't run in this review. Re-run the review to get a score.
Show as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.7 s |
| May 16, 2026 | 3.6 s |
| May 23, 2026 | 3.6 s |
| May 30, 2026 | 3.5 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.7 s |
| Jun 20, 2026 | 3.8 s |
| Jun 27, 2026 | 3.8 s |
| Jul 4, 2026 | 3.7 s |
| Jul 11, 2026 | 3.9 s |
| Jul 18, 2026 | 4.4 s |
| Jul 25, 2026 | 4.8 s |
| Aug 1, 2026 | 5.3 s |
| Aug 8, 2026 | 5.6 s |
| Aug 15, 2026 | 5.6 s |
| Aug 22, 2026 | 6.0 s |
| Aug 29, 2026 | 5.8 s |
| Sep 5, 2026 | 5.9 s |
| Sep 12, 2026 | 5.4 s |
| Sep 19, 2026 | 4.5 s |
| Sep 26, 2026 | 4.2 s |
| Oct 3, 2026 | 3.9 s |
| Oct 10, 2026 | 4.1 s |
| Oct 17, 2026 | 4.1 s |
| Oct 24, 2026 | 4.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 81 ms |
| May 16, 2026 | 80 ms |
| May 23, 2026 | 80 ms |
| May 30, 2026 | 79 ms |
| Jun 6, 2026 | 79 ms |
| Jun 13, 2026 | 81 ms |
| Jun 20, 2026 | 84 ms |
| Jun 27, 2026 | 83 ms |
| Jul 4, 2026 | 86 ms |
| Jul 11, 2026 | 87 ms |
| Jul 18, 2026 | 84 ms |
| Jul 25, 2026 | 86 ms |
| Aug 1, 2026 | 83 ms |
| Aug 8, 2026 | 84 ms |
| Aug 15, 2026 | 84 ms |
| Aug 22, 2026 | 85 ms |
| Aug 29, 2026 | 86 ms |
| Sep 5, 2026 | 83 ms |
| Sep 12, 2026 | 84 ms |
| Sep 19, 2026 | 79 ms |
| Sep 26, 2026 | 77 ms |
| Oct 3, 2026 | 78 ms |
| Oct 10, 2026 | 78 ms |
| Oct 17, 2026 | 81 ms |
| Oct 24, 2026 | 85 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
Not measured in this review.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on your site (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Real-user LCP: 4.0 s
4.0 sReal visitors wait 4.0 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.
Real-user TTFB: 2.5 s
2.5 sReal visitors wait 2.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 81 ms to 85 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.7 s to 4.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Real-user INP: 85 ms
85 msReal visitors wait 85 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Images and page weight
24 images below the first screen load straight away
24 images further down the page (793 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
4 images in older formats
4 images (326 KiB) 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.
About 0.4 g of CO₂ per visit
0.36 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.36 g of CO₂e: 43.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Page weight: 1.3 MB
1.3 MBYour homepage downloads 1.3 MB on a phone, 1.1 MB of it images (85%). That is a lean page.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Unlabelled dropdowns
1 dropdown has no label.
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (2 elements)
Headings should not be empty: 2 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4, h2 → h4 and h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
32 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 39 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 7 failed. 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.
Title is short (17 characters)
Your title is only 17 characters: “Nagico Insurances”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
7 H1 headlines
There are 7 <h1> headlines (“Explore, Dream and discover With Nagico’s Travel …”, “HOW CAN WE HELP YOU TODAY? Click here to go to ou…” and “Excellent health insurance to fit your lifestyle”). One clear main headline is easier for people and search engines.
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 X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
111 internal links, 6 external
The homepage links to 111 pages on nagico.com and 6 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://www.nagico.com/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.nagico.com/wp-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.
No llms.txt
There is no https://www.nagico.com/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.
2 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.
Text is in the HTML
Your server sends the page's text in the HTML (2,367 words), so crawlers that don't run JavaScript still read it.
Other pages
Your server turned our page checks away
15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.
Best practices
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
4 small tap targets
4 of 20 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
No map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
About 2,242 words of copy
The homepage carries about 2,242 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: “Learn More”.
11 calls to action
The homepage has 11 calls to action, for example “Request a Quote”, “Contact” and “Learn More”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Phone number on the homepage
Your phone number is on the homepage.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
7 other companies contacted
Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
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 nagico.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Azure
Company
- Founded
- 1982
- Headquarters
- Philipsburg
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 23 issues on nagico.com, including 4 speed issues, 5 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.