SEO report for codigee.com
https://codigee.com/ · checked Wed, 11 Nov 2026 16:56 GMT
Fix these first
- H1 headingcritical
“Build as one, deliver as hundreds. Build as one deliver as hundreds. We do what it takes to make it. Experts who make an impact.”
Fix: Use one H1 that states the page topic with its main keyword.
- Question-led contentmedium
No headings phrased as questions.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
- Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- Trust pages (E-E-A-T)medium
Links found to about; missing contact and privacy.
Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.
- Scripts & third partiesmedium
27 script tag(s); files loaded from 1 other domain(s): googletagmanager.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- Imagesmedium
77 image(s).
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- Tap-to-contactmedium
No tel: or mailto: links.
Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.
- Render-blocking resourceshigh
1 blocking script(s) and 4 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
Real-world speed Google PageSpeed
Loading Core Web Vitals from Google… this can take up to 30 seconds.
Authority & backlinks
Looking up which websites link to codigee.com…
Indexing & crawling 100%
Can search engines reach, read and index this page?
- ✓
Status codecritical
The page returned HTTP 200.
- ✓
Indexablecritical
No noindex instruction – the page can appear in search.
- ✓
robots.txthigh
robots.txt found.
Googlebot is allowed to crawl this page.
- ✓
XML sitemaphigh
Sitemap found at https://codigee.com/sitemap.xml with 507 URLs.
Declared in robots.txt.
This page is listed in it.
Most recent lastmod: 2026-11-10.
- ✓
Canonical URLhigh
Canonical: https://codigee.com
Points to this page (self-referencing).
- ✓
Redirectshigh
Loads directly with no redirects.
- ✓
www / non-wwwmedium
www.codigee.com redirects to codigee.com.
- ✓
hreflangmedium
7 hreflang link(s).
All language codes are valid.
Search snippet & sharing 100%
How the page looks in Google results and when shared.
- ✓
Title tagcritical
“Flutter app development company in Poland | Codigee”
About 482px of Google's ~580px desktop width.
- ✓
Meta descriptionhigh
149 characters, ~951px of ~990px.
Good length.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
- ✓
Faviconlow
Favicon linked (Google shows it next to results).
- ✓
Languagelow
lang="en"
Content quality 70%
Is there enough clear, useful text that matches what the page targets?
- ✓
Word countmedium
936 words of main content (inside <main>).
Google has no minimum word count – this is a rough guide to whether the page answers the question in full.
- ✓
Readabilitymedium
Flesch reading ease 72 (plain English), about 9 words per sentence.
- ✓
Topic focushigh
5 of 5 title keywords appear in the main content.
- !
H1 headingcritical
“Build as one, deliver as hundreds. Build as one deliver as hundreds. We do what it takes to make it. Experts who make an impact.”
The H1 shares no keywords with the title.
Fix: Use one H1 that states the page topic with its main keyword.
- !
Heading structuremedium
26 headings for 936 words – a lot for the amount of text.
Levels are in order.
Fix: Use H2s for main sections and H3s inside them, without skipping levels.
- ✗
Text-to-code ratiolow
3% of the HTML is visible text.
Fix: Trim unused markup, inline scripts and builder bloat.
AI search readiness 56%
Can ChatGPT, Claude, Perplexity and Google AI Overviews read, understand and cite this site?
- ✓
AI crawler accesshigh
Search and AI-search crawlers (Googlebot, Bingbot, OAI-SearchBot, Claude-SearchBot, PerplexityBot…) can read this page.
- ✓
Snippet controlshigh
No snippet restrictions – search and AI answers can quote this page.
- ✗
llms.txtlow
No /llms.txt file. It's an optional, emerging convention – few AI tools are confirmed to read it yet, so this is low priority.
Fix: Optionally add /llms.txt: a short Markdown summary of who you are with links to your key pages.
- ✗
Question-led contentmedium
No headings phrased as questions.
Fix: Add headings that match real questions ("How much does…?") followed by a direct one- or two-sentence answer – an easy format for search and AI answers to quote.
- ✓
Entity clarityhigh
Identified as: Organization.
3 official profile link(s) (sameAs).
- ✗
Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- ✗
Trust pages (E-E-A-T)medium
Links found to about; missing contact and privacy.
Fix: Link to About, Contact and Privacy pages from every page – they help visitors, Google and AI tools see who stands behind the content.
Structured data 100%
Machine-readable facts for rich results and AI.
- ✓
JSON-LD present & validhigh
1 JSON-LD block(s): Organization, PostalAddress, WebSite, FAQPage, Question, Answer, WebPage.
All blocks parse correctly.
- ✓
Required propertiesmedium
Key types include Google's required properties.
Google now shows FAQ rich results only for well-known government and health sites, but the markup still helps machines read your Q&As.
Links 88%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
80 internal and 16 external links.
- !
Anchor text qualitymedium
Same text used for different pages: “read the case”.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
- ✓
Broken links (sample)high
Checked 12 internal link(s).
No broken links found.
Performance 54%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
35 ms until the first response from our checker, including connection setup (Google rates TTFB good under 0.8 s, poor over 1.8 s).
- !
HTML sizemedium
254 kB of HTML.
Fix: Remove inline bloat, base64 images and unused markup.
- i
Compressionmedium
Couldn't be measured from our server (our fetch decodes compressed pages before we see them). Check in your browser's developer tools that HTML is sent with br or gzip.
- !
Render-blocking resourceshigh
1 blocking script(s) and 4 stylesheet(s) in <head>.
Fix: Add defer to scripts, inline critical CSS and load the rest asynchronously.
- ✗
Scripts & third partiesmedium
27 script tag(s); files loaded from 1 other domain(s): googletagmanager.com.
Fix: Remove unused tracking and widget scripts; every third party adds connection time.
- ✗
Imagesmedium
77 image(s).
5 without width/height – can cause layout shift (CLS).
The first image is lazy-loaded – if it's the main (LCP) image, that delays it. Don't lazy-load images visible on arrival.
70 use WebP/AVIF or responsive srcset.
Fix: Give every image width and height, lazy-load images below the fold (but not the main image) and serve WebP/AVIF.
- ✓
Cachinglow
Cache-Control: s-maxage=31536000
- ✓
HTTP/3low
Server advertises HTTP/3 (faster on mobile networks).
Security 83%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✓
HTTP → HTTPS redirecthigh
http:// redirects to https://.
- ✓
HSTSmedium
HSTS: max-age=31536000
- ✗
Security headerslow
Present: none.
Fix: Add X-Content-Type-Options, Referrer-Policy, Permissions-Policy and X-Frame-Options (or a CSP).
- ✗
Server fingerprintlow
X-Powered-By reveals “Next.js”.
Fix: Remove X-Powered-By so attackers can't see your software versions.
Mobile & accessibility 83%
Usable on phones and by everyone – Google indexes the mobile version.
- ✓
Mobile viewportcritical
viewport: width=device-width, initial-scale=1
- ✓
Image alt textmedium
All 77 images have alt text.
- ✓
Form labelsmedium
All 11 form fields are labelled.
- ✓
Link nameslow
Every link has a readable name.
- ✗
Tap-to-contactmedium
No tel: or mailto: links.
Fix: Add a tap-to-call or tap-to-email button so phone visitors can contact you instantly.
Local SEO not scored
This site doesn't look like a local business, so these checks are shown for information and not scored.
- i
LocalBusiness markuphigh
No LocalBusiness structured data.
- i
Contact details on pagemedium
No phone number found.
No postcode found (fine for service-area businesses).
- i
Map & directionslow
No map or directions link.