Website review, no card needed

sadaqatgroup.net logo

sadaqatgroup.net website review

Visit site (opens in a new tab)Reviewed 26 October 202654 issues · 95 checks

This review found 54 issues worth fixing on sadaqatgroup.net, 26 of them high impact, across 95 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
10.0 s8.3 sMay 2Oct 179.2 s
Show as table
DateReal-visitor load time (LCP)
May 2, 20269.0 s
May 9, 20268.9 s
May 16, 20268.9 s
May 23, 20269.1 s
May 30, 20269.8 s
Jun 6, 20269.1 s
Jun 13, 20268.8 s
Jun 20, 20268.7 s
Jun 27, 20268.5 s
Jul 4, 20269.2 s
Jul 11, 20269.2 s
Jul 18, 20268.9 s
Jul 25, 20269.0 s
Aug 1, 20269.0 s
Aug 8, 20269.0 s
Aug 15, 20269.5 s
Aug 22, 20269.3 s
Aug 29, 20269.2 s
Sep 5, 20269.1 s
Sep 12, 20269.1 s
Sep 19, 20268.8 s
Sep 26, 20268.8 s
Oct 3, 20269.1 s
Oct 10, 20269.6 s
Oct 17, 20269.2 s
Real-visitor tap response (INP)75th percentile, phones
576 ms307 msMay 2Oct 17529 ms
Show as table
DateReal-visitor tap response (INP)
May 2, 2026545 ms
May 9, 2026469 ms
May 16, 2026359 ms
May 23, 2026414 ms
May 30, 2026338 ms
Jun 6, 2026461 ms
Jun 13, 2026482 ms
Jun 20, 2026525 ms
Jun 27, 2026532 ms
Jul 4, 2026487 ms
Jul 11, 2026519 ms
Jul 18, 2026501 ms
Jul 25, 2026412 ms
Aug 1, 2026455 ms
Aug 8, 2026530 ms
Aug 15, 2026476 ms
Aug 22, 2026532 ms
Aug 29, 2026524 ms
Sep 5, 2026405 ms
Sep 12, 2026427 ms
Sep 19, 2026512 ms
Sep 26, 2026536 ms
Oct 3, 2026542 ms
Oct 10, 2026538 ms
Oct 17, 2026529 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

Full-page screenshot of sadaqatgroup.net (desktop) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. sadaqatgroup.net at 1.0 s1.0 s
  2. sadaqatgroup.net at 1.9 s1.9 s
  3. sadaqatgroup.net at 2.9 s2.9 s
  4. sadaqatgroup.net at 3.9 s3.9 s
  5. sadaqatgroup.net at 4.9 s4.9 s
  6. sadaqatgroup.net at 5.8 s5.8 s
  7. sadaqatgroup.net at 6.8 s6.8 s
  8. sadaqatgroup.net at 7.8 s7.8 s

Speed

14 to fix47
  • Use efficient cache lifetimes

    18.1 s · 5.6 MB

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

  • Render-blocking requests

    9.3 s

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

  • Reduce unused JavaScript

    6.9 s · 2.2 MB

    About 2.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.9 s faster on a phone.

  • Reduce unused CSS

    4.5 s · 902 KiB

    About 902 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 4.5 s faster on a phone.

  • Improve image delivery

    1.6 s · 2.0 MB

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

  • Minify JavaScript

    1.2 s · 272 KiB

    272 KiB could be saved by minifying JavaScript.

  • Mobile performance score: 47

    47/100

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

  • Main-thread work: 4.7 s

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

  • 6 third-party services on the page

    6 third-party services load with your homepage (Wistia, Google CDN and Google Maps and others), adding 1.0 MB and 986 ms of main-thread time.

  • Wistia adds 804 ms

    804 ms

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

  • Minify CSS

    460 ms · 114 KiB

    114 KiB could be saved by minifying CSS.

  • Document request latency

    336 KiB

    The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

  • 2,784 HTML elements

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

  • Google CDN adds 97 ms

    97 ms

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

  • 11 long tasks on the main thread

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

  • Font display

    100 ms

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

  • Legacy JavaScript

    57 KiB

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

1 checks passed
  • Server response: 22 ms

    22 ms

    Your server sent the HTML in 22 ms, well inside Google's 600 ms guideline.

Core Web Vitals

11 to fix33
  • 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: 11.7 s

    11.7 s

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

  • Real-user FCP: 9.5 s

    9.5 s

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

  • Real-user TTFB: 3.2 s

    3.2 s

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

  • First Contentful Paint: 11.5 s

    11.5 s

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

  • Largest Contentful Paint: 27.6 s

    27.6 s

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

  • Time to Interactive: 27.7 s

    27.7 s

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

  • Speed Index: 13.1 s

    13.1 s

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

  • Real-user INP: 399 ms

    399 ms

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

  • Total Blocking Time: 337 ms

    337 ms

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

  • 20 images without width and height

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

  • Tap response (INP) held steady for real visitors

    +5%

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

  • Largest content (LCP) held steady for real visitors

    +5%

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

2 checks passed
  • Real-user CLS: 0.08

    0.08

    For real visitors the layout shifts by 0.08 (75th percentile). Good is under 0.1.

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

Images and page weight

5 to fix18
  • Page weight: 7.1 MB in 137 requests

    7.1 MB

    Your homepage downloads 7.1 MB in 137 requests on a phone: images 2.7 MB (24), scripts 2.6 MB (55) and stylesheets 1,014 KiB (29). Under 2 MB keeps phones on slow connections fast.

  • 2 images over 500 KB

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

  • 2 images far larger than shown

    978 KiB

    2 images are downloaded at several times the size a phone draws them, for example photo-collage.png-1024x1024-1.png at 1,024 px wide, shown at 116 px. Resized copies would save about 978 KiB.

  • 7 images in older formats

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

  • 2 images below the first screen load straight away

    2 images further down the page (1.3 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 2.0 g of CO₂ per visit

    2.02 g

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

Accessibility

11 to fixGoogle 7887
  • Images must have alternative text (1 element)

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

  • Malformed lists

    Some lists contain elements other than list items, which screen readers announce wrongly.

  • 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 (91 elements)

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

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • Page should contain a level-one heading (1 element)

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

  • 15 links without text

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

  • 4 form fields without a label

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

  • Alternative text of images should not be repeated as text (5 elements)

    Alternative text of images should not be repeated as text: 5 elements on the page fail this check, rated minor by axe-core.

  • Headings should not be empty (1 element)

    Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

  • Headings skip levels

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

1 checks passed
  • 41 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 41 passed and 11 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

5 to fixGoogle 8566
  • 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.

  • Title is long (97 characters)

    Your title is 97 characters, so Google will cut it off around 60: “Sadaqat Limited – A vertically integrated textile manufacturer & exporter in Faisalabad, …”.

  • 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 X (Twitter) card tag

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

  • 42 internal links, 29 external

    The homepage links to 42 pages on sadaqatgroup.net and 29 external pages.

3 checks passed
  • Canonical URL set

    The canonical URL is https://sadaqatgroup.com/.

  • robots.txt in place

    robots.txt is in place.

  • XML sitemap found

    Your XML sitemap is reachable at https://sadaqatgroup.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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://sadaqatgroup.com/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 (6,556 words), so crawlers that don't run JavaScript still read it.

Other pages

2 to fix90
  • 10 pages without a meta description

    https://sadaqatgroup.com/vtour, https://sadaqatgroup.com/spinning, https://sadaqatgroup.com/weaving-2, https://sadaqatgroup.com/yarn-dyed, https://sadaqatgroup.com/woven-garments-2 and https://sadaqatgroup.com/knitted-2 and 4 others have no meta description, so Google writes the search snippet from whatever text it finds.

  • 4 pages without an H1

    https://sadaqatgroup.com/vtour, https://sadaqatgroup.com/knitted-2, https://sadaqatgroup.com/workwear and https://sadaqatgroup.com/jobs have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 internal pages checked

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

5 checks passed
  • Linked pages load

    All 10 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 10 pages that loaded have a <title>.

Best practices

2 to fixGoogle 6978
  • 1 broken image

    1 image failed to load on a phone, for example https://sadaqatgroup.com/wp-content/themes/beglideimages/logo-black.png.

  • 1 JavaScript error while loading

    1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • Missing source maps

    Large scripts ship without source maps.

  • 1 low-resolution image

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

  • Browser-reported issues

    Chrome logged issues while loading the page (“Mixed content”).

2 checks passed
  • Tap targets are thumb-sized

    9 of 10 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix60
  • 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.

  • Thin social proof

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

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • Phone number is not tap-to-call

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

  • 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 1,249 words of copy

    The homepage carries about 1,249 words of visible text.

2 checks passed
  • 1 call to action

    The homepage has 1 call to action, for example “Contact”.

  • 1 short form

    A short form (5 fields at most) is right on the homepage, asking for an email.

Privacy and tracking

  • 2 cookies set on arrival

    2

    Opening the homepage sets 2 cookies (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.

  • 10 other companies contacted

    Loading the homepage contacts 10 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • No known trackers before consent

    No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).

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 sadaqatgroup.net, 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
jQuery

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 54 issues on sadaqatgroup.net, including 25 speed issues, 5 SEO issues and 3 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25