Website review, no card needed
techvie.io website review
Visit site (opens in a new tab)Reviewed 10 November 202629 issues · 76 checks
This review found 29 issues worth fixing on techvie.io, 10 of them high impact, across 76 checks. The most urgent: use efficient cache lifetimes. 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
Speed
Use efficient cache lifetimes
2.1 s · 1.5 MB77 files are served with short cache lifetimes, so returning visitors download them again (1.5 MB).
Render-blocking requests
2.9 s29 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.9 s.
Reduce unused CSS
1.1 s · 225 KiBAbout 225 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Main-thread work: 7.4 s
A phone's processor spends 7.4 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 73
73/100Your mobile performance score is 73. Pages that score under 90 lose visitors before the first paint.
Font display
350 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 350 ms).
Improve image delivery
300 ms · 23 KiB1 image could be 23 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.
Minify CSS
150 ms · 23 KiB23 KiB could be saved by minifying CSS.
Reduce unused JavaScript
81 KiBAbout 81 KiB of JavaScript is downloaded but never used on this page.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 73 ms. During a long task the page ignores taps.
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
1 third-party service on the page
1 third-party service load with your homepage (Google Fonts), adding 45 KiB and 2 ms of main-thread time.
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
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Speed Index: 17.9 s
17.9 sVisually, the page fills in at 17.9 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 3.9 s
3.9 sYour largest element takes 3.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Strategy That Starts with What You Know”. Most of its time is element render delay (8.2 s).
First Contentful Paint: 2.9 s
2.9 sThe first text or image appears after 2.9 s on a phone. Good is under 1.8 s.
Time to Interactive: 3.9 s
3.9 sThe page becomes fully interactive after 3.9 s. Good is under 3.8 s.
2 images without width and height
2 images have no width and height attributes, so the layout jumps as each one loads.
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.
2 checks passed
Cumulative Layout Shift: 0.029
0.029The layout barely moves while loading (CLS 0.029, 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.
Images and page weight
About 0.4 g of CO₂ per visit
0.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.44 g of CO₂e: 53.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
4 checks passed
Page weight: 1.6 MB in 87 requests
1.6 MBYour homepage downloads 1.6 MB in 87 requests on a phone: fonts 789 KiB (11), scripts 328 KiB (35) and stylesheets 293 KiB (34). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
7 text elements with low contrast
7 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
13 links without text
13 visible links have no text or label, so screen readers cannot say where they go.
6 form fields without a label
6 form fields have no label, so screen readers announce an empty box and autofill guesses.
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
1 checks passed
42 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 42 passed and 4 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (14 characters)
Your title is only 14 characters: “Home - Techvie”. Between 30 and 65 characters leaves room to say what you do and for whom.
No robots.txt
There is no robots.txt at techvie.io/robots.txt, the first file search crawlers ask for.
5 internal links, 2 external
The homepage links to 5 pages on techvie.io and 2 external pages.
5 checks passed
Meta description: 129 characters
Your meta description is 129 characters: “Techvie was created for people like you — who’ve succeeded in traditional systems, and now need to make sense of what c…”.
Canonical URL set
The canonical URL is https://techvie.io/.
Structured data in place
Structured data found: Article, ImageObject, Organization, Person and WebPage.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
XML sitemap found
Your XML sitemap is reachable at https://techvie.io/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.
1 checks passed
Text is in the HTML
Your server sends the page's text in the HTML (402 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without an H1
https://techvie.io/contact-us-01 has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://techvie.io/contact-us-01 has under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
1 page slow to respond
https://techvie.io/contact-us-01 took over 3 s to send its HTML from our server.
1 internal page checked
We fetched 1 page linked from your homepage and read each the way a search engine does.
6 checks passed
Linked pages load
All 1 page we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 1 page that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 1 page that loaded have a <title>.
Best practices
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
5 of 5 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
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 map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
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 306 words of copy
The homepage carries about 306 words of visible text.
3 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Contact”, “Contact now” and “Book a strategy conversation”.
3 short forms
3 short forms (4 fields at most) are right on the homepage, asking for an email.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
8 cookies set on arrival
8Opening the homepage sets 8 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.
2 other companies contacted
Loading the homepage contacts 2 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 techvie.io, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Go beyond the website
What your $25 Growth Playbook adds
This review found 29 issues on techvie.io, including 12 speed issues, 3 SEO issues and 5 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.