meetshah15.github.io website review

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

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

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

1 image could be 76 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 600 ms faster on a phone.

Twitter costs a phone 299 ms of main-thread work and 446 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.

5 third-party services load with your homepage (Twitter, Cloudflare and JSDelivr CDN and others), adding 511 KiB and 310 ms of main-thread time.

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

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

Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

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 6.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Software Engineer at Stellar Cyber with 7+ years of experie…”. Most of its time is element render delay (3.7 s).

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

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

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

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 meet-photo.jpg at 1,080 px wide, shown at 200 px. Resized copies would save about 59 KiB.

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

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

All page content should be contained by landmarks: 27 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.

Your title is only 29 characters: “Meet Shah - Software Engineer”. Between 30 and 65 characters leaves room to say what you do and for whom.

Your meta description is 317 characters; Google truncates after about 160, so the end of your pitch is cut.

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

The homepage links to 7 pages on meetshah15.github.io and 26 external pages.

There is no https://meetshah.tech/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.

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

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

1 error was logged to the browser console while the page loaded, for example “Cannot read properties of undefined (reading 'register')”.

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

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 946 words of visible text.

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