maxkhalus.com website review

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

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

About 2.1 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 3.9 s faster on a phone.

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

About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.

6 third-party services load with your homepage (Calendly, Stripe and Google Tag Manager and others), adding 3.9 MB and 918 ms of main-thread time.

Calendly costs a phone 666 ms of main-thread work and 3.2 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.

8 long tasks block the main thread while loading, the longest for 734 ms. During a long task the page ignores taps.

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 600 ms).

A phone's processor spends 2.6 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

Polyfills for old browsers add 36 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 250 ms faster on a phone.

14 KiB could be saved by minifying CSS.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

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

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

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

Scripts block taps and scrolling for 995 ms in total while the page loads. Good is under 200 ms.

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.

Your homepage downloads 5.9 MB in 95 requests on a phone: scripts 2.7 MB (27), stylesheets 2.2 MB (41) and fonts 860 KiB (14). Under 2 MB keeps phones on slow connections fast.

1 image (89 KiB) is 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.

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

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Headings skip levels (h3 → h6), which makes the page harder to scan with a screen reader.

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

Your title is 77 characters, so Google will cut it off around 60: “Max Khalus: Copywriter and Email Marketing Specialist for B2B Lead Generation”.

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

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 17 pages on maxkhalus.com and 25 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 /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.

/landing-page-copywriter/lingocoin-landing-page, /landing-page-copywriter/lingocoin-landing-page/.com/saas-articles/ai-marketing-platform-comparison-posts, /emails/lead-warm-up-emails-for-trading-group, /emails/mass-cold-outreach-campaign, /emails/promo-email-campaigns-for-trading-group and /saas-articles/ai-ecommerce-lead-magnet and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example /landing-page-copywriter/lingocoin-landing-page, whose canonical is /landing-pages/landing-page-real-estate-rewards-platform. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/landing-page-copywriter/lingocoin-landing-page, /landing-page-copywriter/lingocoin-landing-page/.com/saas-articles/ai-marketing-platform-comparison-posts, /emails/lead-warm-up-emails-for-trading-group, /emails/mass-cold-outreach-campaign, /emails/promo-email-campaigns-for-trading-group and /saas-articles/ai-ecommerce-lead-magnet and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

The page uses 1 deprecated browser API that will stop working in future browsers (“Fenced Frame API is deprecated and scheduled for removal.”).

1 of 5 tappable elements near the top of the page is smaller than 24 px, hard to hit with a thumb.

6 errors were logged to the browser console while the page loaded, for example “Access to font at 'https://www.maxkhalus.com/wp-content/uploads/elementor/google-fonts/fonts/archivo-k3kpo8udi-1m0wlsv9…”.

Chrome logged issues while loading the page (“Cookie”).

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

The homepage has only about 76 words of visible text; thin pages give Google and first-time buyers little to go on.

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

Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 4 cookies, 1 of them by other companies (measured from a US location before any click).

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 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.