thevertical.pk website review

Framer CDN costs a phone 1.7 s of main-thread work and 4.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

About 463 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

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

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

8 third-party services load with your homepage (Framer CDN, ContentSquare and Google Tag Manager and others), adding 4.9 MB and 2.6 s of main-thread time.

8 images could be 609 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 650 ms faster on a phone.

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 700 ms.

ContentSquare costs a phone 348 ms of main-thread work and 185 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.

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

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

smartarget.online costs a phone 124 ms of main-thread work and 295 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.

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

Polyfills for old browsers add 13 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.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

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

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

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

Real visitors wait 3.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 207 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.

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

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

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 194 ms to 211 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 5.0 MB in 185 requests on a phone: images 3.3 MB (57), scripts 1.5 MB (97) and fonts 221 KiB (10). Under 2 MB keeps phones on slow connections fast.

14 images further down the page (735 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images are downloaded at several times the size a phone draws them, for example UrQqewjnRWVW1vMmm3dcpF3MF4.svg at 1,219 px wide, shown at 390 px. Resized copies would save about 22 KiB.

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

Images must have alternative text: 1 element on the page fails this check, rated critical by axe-core.

19 elements hidden from screen readers can still receive keyboard focus.

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

Scrollable region must have keyboard access: 2 elements on the page fail this check, rated serious by axe-core.

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

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

1 visible link has no text or label, so screen readers cannot say where it goes.

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

Your title is 69 characters, so Google will cut it off around 60: “The Vertical – Premier Construction and Development Company in Lahore”.

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

There are 3 <h1> headlines (“fastest developer of pakistan”, “fastest developer of pakistan” and “fastest developer of pakistan”). One clear main headline is easier for people and search engines.

The homepage links to 115 pages on thevertical.pk and 20 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://thevertical.pk/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://thevertical.pk/projects/project-183, https://thevertical.pk/projects/v6-business-centre, https://thevertical.pk/projects/the-grand-vertical, https://thevertical.pk/projects/elevation and https://thevertical.pk/projects/94-business-centre all use the title “The Vertical”. Search engines can't tell which page to show for a search, so each competes with the others.

https://thevertical.pk/projects/project-183, https://thevertical.pk/projects/v6-business-centre, https://thevertical.pk/projects/the-grand-vertical, https://thevertical.pk/projects/elevation and https://thevertical.pk/projects/94-business-centre use the same meta description. A description written for each page earns more clicks.

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

12 of 16 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 “Failed to load resource: net::ERR_FAILED”.

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.

Social proof on the homepage: 2 trust badges. Pairing it with named testimonials or customer logos makes it far more convincing.

Your longest form asks for 19 fields (7 required). Every extra field lowers completion.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel (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 7 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 20 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.