kommol.com website review

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

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

4 files are served with short cache lifetimes, so returning visitors download them again (131 KiB).

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

About 203 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 900 ms faster on a phone.

Your mobile performance score is 65. Pages that score under 90 lose visitors before the first paint.

7 third-party services load with your homepage (jQuery CDN, Google Tag Manager and Google Maps and others), adding 520 KiB and 345 ms of main-thread time.

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

About 19 KiB of CSS is downloaded but never applied on this page.

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.

Your largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “WE BUILD LEADERSHIP TEAMS FOR THE WORLD’S MOST EXCITING NEW…”.

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

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

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

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

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

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 131 requests on a phone: images 5.2 MB (99), scripts 539 KiB (17) and fonts 117 KiB (3). Under 2 MB keeps phones on slow connections fast.

40 images (2.7 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.

20 images further down the page (1.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

4 images are downloaded at several times the size a phone draws them, for example glofox-client-logo.png at 2,274 px wide, shown at 90 px. Resized copies would save about 338 KiB.

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

4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

8 visible links have no text or label, so screen readers cannot say where they go.

1 element hidden from screen readers can still receive keyboard focus.

Headings skip levels (h2 → h5, h2 → h4 and h2 → h4), 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 only 13 characters: “Home | Kommol”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 20 pages on kommol.com and 37 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://kommol.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.

https://kommol.com/our-story, https://kommol.com/clients, https://kommol.com/kore, https://kommol.com/leadership-in-lockdown, https://kommol.com/tough-love-report and https://kommol.com/team and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://kommol.com/clients, https://kommol.com/leadership-in-lockdown, https://kommol.com/team, https://kommol.com/contact, https://kommol.com/words-of-wisdom and https://kommol.com/events/summer-party-2016 and 1 other have 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.

We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.

9 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://data.stbuttons.click/data' from origin 'https://kommol.com' has been blocked by CO…”.

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

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

Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

The homepage shows no opening hours. If customers visit or call, show when.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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 2,884 words of visible text.

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