SEO report for solveit.dev
https://solveit.dev/ · checked Wed, 11 Nov 2026 09:04 GMT
Fix these first
- LocalBusiness markuphigh
No LocalBusiness structured data.
Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.
Also fixes: Entity clarity
- JSON-LD present & validhigh
No JSON-LD structured data.
Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).
- H1 headingcritical
“We build mobile and web apps”
Fix: Use one H1 that states the page topic with its main keyword.
- Mobile viewportcritical
viewport: width=device-width, height=device-height, initial-scale=1, maximum-scale=1, shrink-to-fit=no – blocks pinch-zoom
Fix: Use <meta name="viewport" content="width=device-width, initial-scale=1"> and allow zoom.
- Freshness signalsmedium
No published/updated date found.
Fix: Show a 'last updated' date and add dateModified to your structured data.
- Anchor text qualitymedium
Same text used for different pages: “explore more”.
Fix: Make every link text describe its destination, e.g. “logo design prices” instead of “click here”.
- HSTSmedium
No Strict-Transport-Security header.
Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.
- Meta descriptionhigh
176 characters, ~1101px of ~990px.
Fix: Write a 140–155 character description that answers the searcher's question and invites the click.
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 solveit.dev…
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://solveit.dev/sitemap.xml with 204 URLs.
Declared in robots.txt.
This page is listed in it.
Most recent lastmod: 2026-11-04T09:35:34.005Z.
- ✓
Canonical URLhigh
Canonical: https://solveit.dev/
Points to this page (self-referencing).
- ✓
Redirectshigh
Loads directly with no redirects.
- ✓
www / non-wwwmedium
www.solveit.dev redirects to solveit.dev.
Search snippet & sharing 88%
How the page looks in Google results and when shared.
- ✓
Title tagcritical
“SolveIt | Full-Cycle Software Development Company”
About 465px of Google's ~580px desktop width.
- !
Meta descriptionhigh
176 characters, ~1101px of ~990px.
Long – Google will probably truncate it.
Google sometimes rewrites descriptions to match the search; a good one is still used most often.
Fix: Write a 140–155 character description that answers the searcher's question and invites the click.
- ✓
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
787 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 55 (fairly easy), about 12 words per sentence.
- ✓
Topic focushigh
4 of 5 title keywords appear in the main content (missing: cycle).
- !
H1 headingcritical
“We build mobile and web apps”
The H1 shares no keywords with the title.
Fix: Use one H1 that states the page topic with its main keyword.
- !
Heading structuremedium
31 headings for 787 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
2% 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
3 heading(s) phrased as questions, e.g. “What’s new in our blog?”.
- ✗
Entity clarityhigh
No Organization / LocalBusiness structured data – search engines and AI have to guess who runs this site.
Fix: Add Organization or LocalBusiness JSON-LD with name, url, logo, contact details and sameAs links to your official profiles.
- ✗
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 and contact; missing 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 0%
Machine-readable facts for rich results and AI.
- ✗
JSON-LD present & validhigh
No JSON-LD structured data.
Fix: Add JSON-LD describing the business and the page (Organization/LocalBusiness, WebSite, WebPage or Article, BreadcrumbList).
Links 75%
Internal linking, anchor text and broken links.
- ✓
Internal linkinghigh
69 internal and 17 external links.
- ✗
Anchor text qualitymedium
Same text used for different pages: “explore more”.
1 vague link(s) like “click here” or “read more”.
8 link(s) with no text at all.
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 80%
Speed signals from the HTML and server. Real-user Core Web Vitals load below.
- ✓
Server response (TTFB)high
429 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
283 kB of HTML.
Fix: Remove inline bloat, base64 images and unused markup.
- ✓
Compressionmedium
Compressed with gzip.
- ✓
Render-blocking resourceshigh
0 blocking script(s) and 2 stylesheet(s) in <head>.
- !
Scripts & third partiesmedium
18 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
63 image(s).
All images reserve their space.
4 image(s) after the first three aren't lazy-loaded.
The first image is lazy-loaded – if it's the main (LCP) image, that delays it. Don't lazy-load images visible on arrival.
46 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, stale-while-revalidate
- i
HTTP/3low
Couldn't be confirmed from our server – the alt-svc header that advertises HTTP/3 isn't always visible to it. Your site is on Cloudflare, which offers HTTP/3 under Network settings.
Security 67%
Visitor safety signals that browsers and Google check.
- ✓
HTTPScritical
Secure HTTPS with no mixed content.
- ✓
HTTP → HTTPS redirecthigh
http:// redirects to https://.
- ✗
HSTSmedium
No Strict-Transport-Security header.
Fix: Add Strict-Transport-Security: max-age=63072000; includeSubDomains.
- ✗
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 65%
Usable on phones and by everyone – Google indexes the mobile version.
- !
Mobile viewportcritical
viewport: width=device-width, height=device-height, initial-scale=1, maximum-scale=1, shrink-to-fit=no – blocks pinch-zoom
Fix: Use <meta name="viewport" content="width=device-width, initial-scale=1"> and allow zoom.
- ✓
Image alt textmedium
All 63 images have alt text.
- ✗
Link nameslow
8 link(s) have no readable name for screen readers.
Fix: Add text or aria-label to icon-only links.
- ✓
Tap-to-contactmedium
One-tap contact: phone and email.
Local SEO 33%
Signals that help you appear in Google Maps and 'near me' searches.
- ✗
LocalBusiness markuphigh
No LocalBusiness structured data.
Fix: Add LocalBusiness JSON-LD with address or areaServed, telephone, geo, opening hours and url.
- ✓
Contact details on pagemedium
A UK phone number is shown.
No postcode found (fine for service-area businesses).
An email link is shown.
- ✗
Map & directionslow
No map or directions link.
Fix: Add a Google Maps directions link so customers can find you.