Website review, no card needed
hristoff.com website review
Visit site (opens in a new tab)Reviewed 10 November 202615 issues · 50 checks
This review found 15 issues worth fixing on hristoff.com, 3 of them high impact, across 50 checks. The most urgent: no call to action on the first screen. 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
83BClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
900 ms · 253 KiB5 files are served with short cache lifetimes, so returning visitors download them again (253 KiB).
Font display
950 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 950 ms).
Render-blocking requests
550 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 550 ms.
Reduce unused CSS
150 ms · 16 KiBAbout 16 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Document request latency
47 KiBThe HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.
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: 98
98/100Your mobile performance score is 98. That is in Google's “good” band (90 and up).
Server response: 239 ms
239 msYour server sent the HTML in 239 ms, well inside Google's 600 ms guideline.
Main-thread work: 0.1 s
A phone's processor spends 0.1 s on main-thread work while loading, 7 ms of it running JavaScript. That is comfortably low.
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
Speed Index: 3.4 s
3.4 sVisually, the page fills in at 3.4 s (Speed Index), inside the 3.4 s “good” threshold.
Largest Contentful Paint: 2.1 s
2.1 sYour largest element renders in 2.1 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Adept at both high-level strategy and hands-on execution, I…”.
First Contentful Paint: 1.3 s
1.3 sThe first text or image appears after 1.3 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.047
0.047The layout barely moves while loading (CLS 0.047, good is under 0.1).
Time to Interactive: 2.1 s
2.1 sThe page is fully interactive after 2.1 s.
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
1 image below the first screen load straight away
1 image further down the page (41 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 0.09 g of CO₂ per visit
0.09 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.09 g of CO₂e: 10.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Page weight: 323 KiB in 6 requests
323 KiBYour homepage downloads 323 KiB in 6 requests on a phone: fonts 190 KiB (2), HTML 70 KiB (1) and images 41 KiB (1). That is a lean page.
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Headings skip levels
Headings skip levels (h1 → h3 and h3 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 1 image in the HTML carry an alt attribute.
34 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 35 WCAG 2.2 A/AA and best-practice rules on the phone render: 34 passed and 1 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.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 H1 headlines
There are 2 <h1> headlines (“Ivan Hristoff – personal website” and “Dynamic Senior Product Manager with 10+ years’ ex…”). 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 XML sitemap
No XML sitemap at https://hristoff.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at hristoff.com/robots.txt, the first file search crawlers ask for.
Only 1 internal link
The homepage links to only 1 page on your own site, so visitors and crawlers find few routes into the rest of it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
2 checks passed
Title: 50 characters
Your title is a healthy 50 characters: “Ivan Hristoff – personal website – Product Manager”.
Canonical URL set
The canonical URL is https://hristoff.com/.
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://hristoff.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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (813 words), so crawlers that don't run JavaScript still read it.
Best practices
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 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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Thin social proof
Social proof on the homepage: “8M+ users”. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 812 words of copy
The homepage carries about 812 words of visible text.
1 checks passed
Direct contact links
Visitors can reach you directly: 0 phone links and 2 email links.
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 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 hristoff.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
- Hosting
- SuperHosting.BG Ltd.
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 15 issues on hristoff.com, including 3 speed issues, 7 SEO issues and 4 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.