techzoid.pk website review

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

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

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

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

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

About 183 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.

5 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.0 MB and 597 ms of main-thread time.

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

Google CDN costs a phone 416 ms of main-thread work and 734 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.

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

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

The page has 1,525 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

Your largest element takes 9.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 30.0 s. Good is under 3.8 s.

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

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

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

Scripts block taps and scrolling for 449 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 7.3 MB in 163 requests on a phone: images 3.5 MB (60), fonts 1.9 MB (13) and scripts 1.3 MB (51). Under 2 MB keeps phones on slow connections fast.

2 images weigh 1.3 MB together. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example h3-bg-shape-shadow-1.webp at 1,920 px wide, shown at 390 px. Resized copies would save about 1.2 MB.

18 images further down the page (926 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 2.08 g of CO₂e: 249.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

5 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: 58 elements on the page fail this check, rated moderate by axe-core.

4 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Elements with visible text labels do not have matching accessible names. (19 elements).

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

The homepage links to 43 pages on techzoid.pk and 9 external pages.

Your homepage links to https://techzoid.pk/services, which answers with an error. Visitors hit a dead end and search engines drop it.

https://techzoid.pk/about-us, https://techzoid.pk/our-services, https://techzoid.pk/blog, https://techzoid.pk/skill-development, https://techzoid.pk/contact-us and https://techzoid.pk/contact and 3 others all use the title “TECHZOID - Leading IT Company in Pakistan | Web Development & AI Solu…”. Search engines can't tell which page to show for a search, so each competes with the others.

https://techzoid.pk/about-us, https://techzoid.pk/blog, https://techzoid.pk/skill-development, https://techzoid.pk/contact-us, https://techzoid.pk/contact and https://techzoid.pk/faq and 2 others use the same meta description. A description written for each page earns more clicks.

Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://techzoid.pk/blog, whose canonical is https://techzoid.pk/blogs. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://techzoid.pk/blog, https://techzoid.pk/how-ai-is-revolutionizing-software-development, https://techzoid.pk/day-3-gb-it-delegation-2025-visit-to-islamabad-pakistan, https://techzoid.pk/day-2-gb-it-delegation-2025-visit-to-islamabad-pakistan, https://techzoid.pk/privacy-policy-2 and https://techzoid.pk/terms-of-use have no <h1> headline, so visitors and search engines get no clear main topic.

https://techzoid.pk/contact-us and https://techzoid.pk/contact 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 13 pages linked from your homepage and read each the way a search engine does.

1 image is served at too low a resolution for sharp phone screens.

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 phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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