Website review, no card needed
codean.io website review
Visit site (opens in a new tab)Reviewed 10 November 202617 issues · 79 checks
This review found 17 issues worth fixing on codean.io, 4 of them high impact, across 79 checks. The most urgent: render-blocking 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
90AClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Render-blocking requests
1.3 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.3 s.
Use efficient cache lifetimes
500 ms · 136 KiB7 files are served with short cache lifetimes, so returning visitors download them again (136 KiB).
Reduce unused CSS
130 ms · 14 KiBAbout 14 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 130 ms faster on a phone.
1 third-party service on the page
1 third-party service load with your homepage (Cloudflare), adding 10 KiB and 10 ms of main-thread time.
Legacy JavaScript
10 KiBPolyfills for old browsers add 10 KiB JavaScript that modern phones do not need.
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: 99
99/100Your mobile performance score is 99. That is in Google's “good” band (90 and up).
Main-thread work: 0.3 s
A phone's processor spends 0.3 s on main-thread work while loading, 25 ms of it running JavaScript. That is comfortably low.
Server response: 83 ms
83 msYour server sent the HTML in 83 ms, well inside Google's 600 ms guideline.
Core Web Vitals
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.
6 checks passed
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Speed Index: 2.7 s
2.7 sVisually, the page fills in at 2.7 s (Speed Index), inside the 3.4 s “good” threshold.
Largest Contentful Paint: 1.7 s
1.7 sYour largest element renders in 1.7 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “We find critical vulnerabilities before hackers exploit them”.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Time to Interactive: 1.7 s
1.7 sThe page is fully interactive after 1.7 s.
Images and page weight
About 0.06 g of CO₂ per visit
0.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.06 g of CO₂e: 7.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Page weight: 233 KiB in 9 requests
233 KiBYour homepage downloads 233 KiB in 9 requests on a phone: scripts 139 KiB (5), fonts 48 KiB (1) and HTML 27 KiB (1). That is a lean page.
Accessibility
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
All page content should be contained by landmarks (10 elements)
All page content should be contained by landmarks: 10 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.
Headings should not be empty (3 elements)
Headings should not be empty: 3 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h2 → h4 and h1 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
29 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 34 WCAG 2.2 A/AA and best-practice rules on the phone render: 29 passed and 5 failed. 1 more 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.
Title is short (18 characters)
Your title is only 18 characters: “Home - Codean Labs”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“We find critical vulnerabilities before hackers e…” and “Let’s talk. One short call to explore if our appr…”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
14 internal links, 8 external
The homepage links to 14 pages on codean.io and 8 external pages.
4 checks passed
Canonical URL set
The canonical URL is https://codeanlabs.com/.
Structured data in place
Structured data found: Article, Organization, Person, WebPage and WebSite.
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://codeanlabs.com/wp-sitemap.xml.
AI search readiness
Organization data is thin (1 of 6 facts)
Your Organization JSON-LD is missing url, logo, sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
No llms.txt
There is no /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 (660 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages without a meta description
/pricing, /category/research, /about and /services-ctf have no meta description, so Google writes the search snippet from whatever text it finds.
5 internal pages checked
We fetched 5 pages linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 5 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 5 pages that loaded have a <title>.
Best practices
6 small tap targets
6 of 10 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 “Cannot use import statement outside a module”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Security and trust
1 broken link to your own pages
1 link from your homepage to your own site is broken, for example https://codeanlabs.com/cdn-cgi/l/email-protection (404).
No Content-Security-Policy
No Content-Security-Policy header, the main browser-side defence against injected scripts.
No clickjacking protection
Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.
No X-Content-Type-Options
X-Content-Type-Options: nosniff is missing, so browsers may guess file types.
No Referrer-Policy
No Referrer-Policy header, so full URLs can leak to the sites you link to.
No Permissions-Policy
No Permissions-Policy header to switch off camera, microphone and location for embedded content.
No security.txt
There is no /.well-known/security.txt telling researchers how to report a security problem to you.
5 checks passed
Served over HTTPS
The homepage is served over HTTPS (codeanlabs.com).
Valid certificate (59 days left)
The certificate from Google Trust Services · WE1 verifies for codean.io and is valid for another 59 days.
HSTS enabled
Strict-Transport-Security is set, so browsers always use https.
http:// redirects to https
http://codean.io redirects to the secure version.
HTTP/2 and HTTP/3
The server speaks HTTP/2 and advertises HTTP/3, so browsers load many files over one connection.
Domain and trust
4 checks passed
Domain is 3 years old
3 yearscodeanlabs.com was registered in Jul 2023 through Cloudflare, Inc.. An established domain carries more trust with email providers and search engines.
Certificate issuers are restricted
CAA records allow only digicert.com, letsencrypt.org, pki.goog and ssl.com to issue certificates for codeanlabs.com, so a mis-issued certificate from anyone else is refused.
DNSSEC is on
codeanlabs.com's DNS answers are signed (DNSSEC), so they can't be forged on the way to visitors.
Registered until Jul 2027
codeanlabs.com is registered until Jul 2027.
Content and conversion
Thin social proof
Social proof on the homepage: 3 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.
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 650 words of copy
The homepage carries about 650 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Pricing” and “Book a call”.
5 calls to action
The homepage has 5 calls to action, for example “Pricing”, “Book a call” and “Schedule a 30-minute call”.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Email authentication
Email authentication score: 95/100
Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.
3 checks passed
DMARC policy: reject
DMARC tells receivers to reject mail that fails authentication.
SPF in place (~all)
An SPF record lists your sending servers and marks other mail as suspicious (~all): “v=spf1 include:_spf.google.com include:_spf.omniasoft.network ~all”.
DKIM signing found
A DKIM key is published (selector “google”), so receivers can verify mail really came from you.
Privacy and tracking
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.
1 other company contacted
Loading the homepage contacts 1 host 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).
Upkeep, stack and company
No signs of neglect in what was checked: the copyright year, CMS and plugin versions, and jQuery.
Stack
- CMS
- WordPress 7.1.4
- Framework
- Tailwind CSS
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 17 issues on codean.io, including 2 speed issues, 4 SEO issues and 1 conversion gap. 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.