yankovsky.info website review

5 images could be 2.6 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 12.2 s faster on a phone.

7 files are served with short cache lifetimes, so returning visitors download them again (1.1 MB).

About 279 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.7 s faster on a phone.

About 214 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.3 s faster on a phone.

4 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.2 s.

Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

4 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and Google Fonts and others), adding 3.5 MB and 209 ms of main-thread time.

googleusercontent.com costs a phone 0 ms of main-thread work and 2.6 MB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

Google CDN costs a phone 174 ms of main-thread work and 633 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

1 long task block the main thread while loading, the longest for 75 ms. During a long task the page ignores taps.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

Your largest element takes 19.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

The page becomes fully interactive after 19.5 s. Good is under 3.8 s.

The first text or image appears after 4.8 s on a phone. Good is under 1.8 s.

The layout shifts by 0.395 while loading, so content jumps under the reader's thumb. Good is under 0.1.

Visually, the page fills in at 7.2 s (Speed Index). Good is under 3.4 s.

6 images have no width and height attributes, so the layout jumps as each one loads.

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.

APXyLQfJI6rbXgtAaZ_sJFqtfzZS2fdJDav1FPiLBKVlCBTta21zNm41FnSW weighs 2.2 MB. On a phone connection a single image that size takes seconds.

4 images are downloaded at several times the size a phone draws them, for example APXyLQfJI6rbXgtAaZ_sJFqtfzZS2fdJDav1FPiLBKVlCBTta21zNm41FnSW at 1,280 px wide, shown at 352 px. Resized copies would save about 1.1 MB.

Your homepage downloads 3.5 MB in 32 requests on a phone: images 2.6 MB (8), scripts 529 KiB (10) and stylesheets 223 KiB (3). Under 2 MB keeps phones on slow connections fast.

4 images (2.6 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

3 images further down the page (415 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

By the Sustainable Web Design model, a visit to your homepage emits about 1.00 g of CO₂e: 120.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

6 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 78 elements on the page fail this check, rated moderate by axe-core.

Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

No meta description, so Google writes its own snippet from whatever text it finds.

Your title is only 14 characters: “Nick Yankovsky”. Between 30 and 65 characters leaves room to say what you do and for whom.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

There are 3 <h1> headlines (“Summary”, “Experience” and “Recommendations”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No XML sitemap at https://www.yankovsky.info/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at yankovsky.info/robots.txt, the first file search crawlers ask for.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 9 pages on yankovsky.info and 18 external pages.

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.

There is no https://www.yankovsky.info/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.

/ and https://www.yankovsky.info/home all use the title “Nick Yankovsky”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.yankovsky.info/home and https://www.yankovsky.info/me have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.yankovsky.info/me has no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 2 pages linked from your homepage and read each the way a search engine does.

2 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://play.google.com/log?format=json&hasfast=true&authuser=0' from origin 'https://www.yankovsky…”.

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

There is no form on the homepage, so every lead has to click through to another page first.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 414 words of visible text.

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.

Loading the homepage contacts 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.