waseembashir.com website review

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 700 ms.

4 third-party services load with your homepage (Google Tag Manager, vercel.app and Google Fonts and others), adding 255 KiB and 121 ms of main-thread time.

5 images could be 86 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

About 71 KiB of JavaScript is downloaded but never used on this page.

1 file is served with short cache lifetimes, so returning visitors download them again (6 KiB).

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 KiB could be saved by minifying JavaScript.

14 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.

1 image is downloaded at several times the size a phone draws it, for example hitachi.png at 1,635 px wide, shown at 77 px. Resized copies would save about 51 KiB.

1 image (52 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 0.12 g of CO₂e: 14.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

The homepage links to 50 pages on waseembashir.com and 16 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.waseembashir.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://www.waseembashir.com/courses and https://www.waseembashir.com/coaching 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 23 found) and read each the way a search engine does.

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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