dhamultan.org website review

52 files are served with short cache lifetimes, so returning visitors download them again (4.0 MB).

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

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

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

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

Your mobile performance score is 58 (desktop: 92). Pages that score under 90 lose visitors before the first paint.

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

55 KiB could be saved by minifying JavaScript.

5 third-party services load with your homepage (Google Tag Manager, jQuery CDN and datatables.net and others), adding 429 KiB and 129 ms of main-thread time.

1 long task block the main thread while loading, the longest for 70 ms. During a long task the page ignores taps.

Desktop scores 92 but mobile only 58. A gap that wide usually means heavy scripts and images that hit phones hardest.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB could be saved by minifying CSS.

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 visitors wait 6.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

Your largest element takes 15.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Development Updates Energization of Street Light System at …”.

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

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

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

9 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-24, real Chrome visitors' largest content (lcp) went from 5.0 s to 5.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 4.5 MB in 64 requests on a phone: images 2.5 MB (14), fonts 1.1 MB (5) and scripts 665 KiB (22). Under 2 MB keeps phones on slow connections fast.

5.png weighs 973 KiB. On a phone connection a single image that size takes seconds.

3 images are downloaded at several times the size a phone draws them, for example 5.png at 1,365 px wide, shown at 316 px. Resized copies would save about 1.1 MB.

7 images (1.8 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.

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

3 buttons have no accessible name, so screen readers announce just “button”.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

15 visible links have no text or label, so screen readers cannot say where they go.

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

Your title is only 10 characters: “DHA MULTAN”. Between 30 and 65 characters leaves room to say what you do and for whom.

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

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

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 at https://www.dhamultan.org/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at dhamultan.org/robots.txt, the first file search crawlers ask for.

1 link has no real href, so search engines can't follow it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 53 pages on dhamultan.org and 22 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 /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.

/developed and /developed.php all use the title “Developed Projects”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

/developed, /developed.php, /developing.php, /upcoming.php, /procedures.php and /image.php and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

/developed, /developed.php, /developing.php, /upcoming.php, /procedures.php and /image.php and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

/developed, /developed.php, /developing.php, /upcoming.php and /procedures.php took over 3 s to send their HTML from our server.

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

1 image failed to load on a phone, for example https://ucms.dhamultan.org//uploads/IMG_20260709_WA_0012_Medium_90175659ad.jpg.

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

No Content-Security-Policy header, the main browser-side defence against injected scripts.

The server only offers HTTP/1.1, so browsers open several connections and load files more slowly. Most hosts and CDNs turn on HTTP/2 with a setting.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

1 link go through two or more redirects, for example https://www.dhamultan.org/Developed.php.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

dhamultan.org has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

dhamultan.org's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

The homepage has only about 201 words of visible text; thin pages give Google and first-time buyers little to go on.

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.

DMARC is set to p=none, so mail pretending to be dhamultan.org is still delivered. Add a report address, check the reports, then move to quarantine.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

Before a visitor clicks anything, the page loads Google Ads, 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.