Website review, no card needed
tdap.gov.pk website review
Visit site (opens in a new tab)Reviewed 19 November 202652 issues · 92 checks
This review found 52 issues worth fixing on tdap.gov.pk, 24 of them high impact, across 92 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
51FClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 14.3 s |
| Jun 6, 2026 | 15.1 s |
| Jun 13, 2026 | 15.8 s |
| Jun 20, 2026 | 15.4 s |
| Jun 27, 2026 | 13.7 s |
| Jul 4, 2026 | 13.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.0 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.2 s |
| Aug 15, 2026 | 6.4 s |
| Aug 22, 2026 | 12.3 s |
| Aug 29, 2026 | 12.3 s |
| Sep 5, 2026 | 12.0 s |
| Sep 12, 2026 | 11.9 s |
| Sep 19, 2026 | 11.8 s |
| Sep 26, 2026 | 11.8 s |
| Oct 3, 2026 | 12.0 s |
| Oct 10, 2026 | 11.9 s |
| Oct 17, 2026 | 12.1 s |
| Oct 24, 2026 | 12.8 s |
| Oct 31, 2026 | 12.9 s |
| Nov 7, 2026 | 13.0 s |
| Nov 14, 2026 | 12.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 261 ms |
| Jun 6, 2026 | 269 ms |
| Jun 13, 2026 | 283 ms |
| Jun 20, 2026 | 290 ms |
| Jun 27, 2026 | 322 ms |
| Jul 4, 2026 | 296 ms |
| Jul 11, 2026 | 136 ms |
| Jul 18, 2026 | 133 ms |
| Jul 25, 2026 | 133 ms |
| Aug 1, 2026 | 133 ms |
| Aug 8, 2026 | 134 ms |
| Aug 15, 2026 | 149 ms |
| Aug 22, 2026 | 290 ms |
| Aug 29, 2026 | 314 ms |
| Sep 5, 2026 | 345 ms |
| Sep 12, 2026 | 367 ms |
| Sep 19, 2026 | 343 ms |
| Sep 26, 2026 | 309 ms |
| Oct 3, 2026 | 306 ms |
| Oct 10, 2026 | 278 ms |
| Oct 17, 2026 | 263 ms |
| Oct 24, 2026 | 272 ms |
| Oct 31, 2026 | 291 ms |
| Nov 7, 2026 | 299 ms |
| Nov 14, 2026 | 297 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
Speed
Use efficient cache lifetimes
14.7 s · 5.8 MB680 files are served with short cache lifetimes, so returning visitors download them again (5.8 MB).
Render-blocking requests
13.9 s420 files block the first paint until they finish downloading. Deferring or inlining them could save about 13.9 s.
Improve image delivery
2.6 s · 3.0 MB15 images could be 3.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.6 s faster on a phone.
Reduce unused JavaScript
2.1 s · 457 KiBAbout 457 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.1 s faster on a phone.
Reduce unused CSS
1.1 s · 227 KiBAbout 227 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 25
25/100Your mobile performance score is 25. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.8 s
A phone's processor spends 4.8 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Reduce initial server response time
918 msReduce initial server response time. Google estimates savings of 918 ms on a phone.
Document request latency
900 msThe HTML itself could arrive about 900 ms sooner: redirects, a slow server response or missing compression delay everything after it.
13 long tasks on the main thread
13 long tasks block the main thread while loading, the longest for 680 ms. During a long task the page ignores taps.
1,917 HTML elements
The page has 1,917 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Server response: 1.0 s
1.0 sYour server takes 1.0 s to send the HTML. Google recommends under 600 ms; everything else waits for it.
3 third-party services on the page
3 third-party services load with your homepage (canvasjs.com, Cloudflare and Google Fonts), adding 120 KiB and 57 ms of main-thread time.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify JavaScript
30 ms · 11 KiB11 KiB could be saved by minifying JavaScript.
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
5 KiB5 KiB could be saved by minifying CSS.
Core Web Vitals
Fails Core Web Vitals for real visitors
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.
Real-user LCP: 13.3 s
13.3 sReal visitors wait 13.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 12.2 s
12.2 sReal visitors see the first content after 12.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 5.9 s
5.9 sReal visitors wait 5.9 s for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 9.0 s
9.0 sThe first text or image appears after 9.0 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 38.0 s
38.0 sYour largest element takes 38.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 19.1 s
19.1 sVisually, the page fills in at 19.1 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 39.1 s
39.1 sThe page becomes fully interactive after 39.1 s. Good is under 3.8 s.
Total Blocking Time: 954 ms
954 msScripts block taps and scrolling for 954 ms in total while the page loads. Good is under 200 ms.
Real-user INP: 375 ms
375 msReal visitors wait 375 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.19
0.19For real visitors the layout shifts by 0.19 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.192
0.192The layout shifts by 0.192 while loading, so content jumps under the reader's thumb. Good is under 0.1.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 12% slower for real visitors
+12%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 261 ms to 297 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Largest content (LCP) got 12% faster for real visitors
-12%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 14.3 s to 12.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Images and page weight
Page weight: 9.3 MB in 725 requests
9.3 MBYour homepage downloads 9.3 MB in 725 requests on a phone: images 5.6 MB (38), scripts 1.5 MB (245) and stylesheets 1.3 MB (422). Under 2 MB keeps phones on slow connections fast.
13 images in older formats
13 images (1.2 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.
About 2.6 g of CO₂ per visit
2.65 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.65 g of CO₂e: 317.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
4 tap targets too small
4 tap targets are too small or too close together to hit reliably with a finger.
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (23 elements)
All page content should be contained by landmarks: 23 elements on the page fail this check, rated moderate by axe-core.
The skip-link target should exist and be focusable (1 element)
The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.
14 links without text
14 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 82 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://tdap.gov.pk/wp-sitemap.xml, so Google discovers your pages only by following links.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
198 internal links, 53 external
The homepage links to 198 pages on tdap.gov.pk and 53 external pages.
3 checks passed
Title: 46 characters
Your title is a healthy 46 characters: “Trade Development Authority of Pakistan (TDAP)”.
Canonical URL set
The canonical URL is https://tdap.gov.pk/.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://tdap.gov.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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (681 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages without a meta description
https://tdap.gov.pk/about-tdap, https://tdap.gov.pk/chief-executive, https://tdap.gov.pk/secretary-tdap, https://tdap.gov.pk/tdap-mandate, https://tdap.gov.pk/tdap-organogram and https://tdap.gov.pk/our-offices and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
13 pages without an H1
https://tdap.gov.pk/chief-executive, https://tdap.gov.pk/secretary-tdap, https://tdap.gov.pk/tdap-mandate, https://tdap.gov.pk/tdap-organogram, https://tdap.gov.pk/our-offices and https://tdap.gov.pk/our-team and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 pages slow to respond
https://tdap.gov.pk/about-tdap, https://tdap.gov.pk/chief-executive, https://tdap.gov.pk/secretary-tdap, https://tdap.gov.pk/tdap-mandate, https://tdap.gov.pk/tdap-organogram and https://tdap.gov.pk/our-offices and 9 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 72 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.
2 checks passed
Tap targets are thumb-sized
14 of 16 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No phone number on the homepage
A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 300 words of copy
The homepage carries about 300 words of visible text.
2 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact Us” and “Join Amazon as Pakistani Seller”.
Analytics in place
Analytics detected: Cloudflare Web Analytics.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads 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.
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
No consent tool detected
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.
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at tdap.gov.pk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Framework
- React
- Hosting
- Cloudflare
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 52 issues on tdap.gov.pk, including 25 speed issues, 7 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.