Website review, no card needed
ghazibrothers.com website review
Visit site (opens in a new tab)Reviewed 31 October 202634 issues · 76 checks
This review found 34 issues worth fixing on ghazibrothers.com, 14 of them high impact, across 76 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
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 7.8 s |
| May 16, 2026 | 7.5 s |
| May 23, 2026 | 7.5 s |
| May 30, 2026 | 7.3 s |
| Jun 6, 2026 | 7.7 s |
| Jun 13, 2026 | 7.7 s |
| Jun 20, 2026 | 7.7 s |
| Jun 27, 2026 | 7.8 s |
| Jul 4, 2026 | 7.5 s |
| Jul 11, 2026 | 7.5 s |
| Jul 18, 2026 | 7.7 s |
| Jul 25, 2026 | 7.7 s |
| Aug 1, 2026 | 8.4 s |
| Aug 8, 2026 | 8.6 s |
| Aug 15, 2026 | 8.4 s |
| Aug 22, 2026 | 8.4 s |
| Aug 29, 2026 | 8.6 s |
| Sep 5, 2026 | 9.3 s |
| Sep 12, 2026 | 10.0 s |
| Sep 19, 2026 | 10.6 s |
| Sep 26, 2026 | 11.1 s |
| Oct 3, 2026 | 11.3 s |
| Oct 10, 2026 | 11.5 s |
| Oct 17, 2026 | 11.4 s |
| Oct 24, 2026 | 10.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 145 ms |
| May 16, 2026 | 144 ms |
| May 23, 2026 | 143 ms |
| May 30, 2026 | 145 ms |
| Jun 6, 2026 | 145 ms |
| Jun 13, 2026 | 141 ms |
| Jun 20, 2026 | 149 ms |
| Jun 27, 2026 | 148 ms |
| Jul 4, 2026 | 149 ms |
| Jul 11, 2026 | 150 ms |
| Jul 18, 2026 | 142 ms |
| Jul 25, 2026 | 137 ms |
| Aug 1, 2026 | 127 ms |
| Aug 8, 2026 | 129 ms |
| Aug 15, 2026 | 130 ms |
| Aug 22, 2026 | 130 ms |
| Aug 29, 2026 | 136 ms |
| Sep 5, 2026 | 136 ms |
| Sep 12, 2026 | 137 ms |
| Sep 19, 2026 | 138 ms |
| Sep 26, 2026 | 135 ms |
| Oct 3, 2026 | 134 ms |
| Oct 10, 2026 | 133 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
How it loaded on a phone
0.8 s
1.6 s
2.4 s
3.1 s
3.9 s
4.7 s
5.5 s
6.3 s
Speed
Use efficient cache lifetimes
5.7 s · 4.7 MB105 files are served with short cache lifetimes, so returning visitors download them again (4.7 MB).
Render-blocking requests
3.2 s52 files block the first paint until they finish downloading. Deferring or inlining them could save about 3.2 s.
Mobile performance score: 61
61/100Your mobile performance score is 61. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
650 ms · 302 KiB3 images could be 302 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.
Reduce unused JavaScript
760 ms · 157 KiBAbout 157 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 760 ms faster on a phone.
Reduce unused CSS
600 ms · 120 KiBAbout 120 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Main-thread work: 2.1 s
A phone's processor spends 2.1 s on main-thread work while loading, 850 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, cdn-cookieyes.com and Google Fonts and others), adding 303 KiB and 292 ms of main-thread time.
Legacy JavaScript
200 ms · 35 KiBPolyfills for old browsers add 35 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 200 ms faster on a phone.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 120 ms. During a long task the page ignores taps.
Minify CSS
10 ms · 5 KiB5 KiB could be saved by minifying CSS.
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: 71 ms
71 msYour server sent the HTML in 71 ms, well inside Google's 600 ms guideline.
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: 14.0 s
14.0 sReal visitors wait 14.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 11.1 s
11.1 sReal visitors see the first content after 11.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 6.3 s
6.3 sReal visitors wait 6.3 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 14.0 s
14.0 sYour largest element takes 14.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 16.8 s
16.8 sThe page becomes fully interactive after 16.8 s. Good is under 3.8 s.
Speed Index: 9.3 s
9.3 sVisually, the page fills in at 9.3 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) got 44% slower for real visitors
+44%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 7.8 s to 10.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
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) held steady for real visitors
-8%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 145 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Total Blocking Time: 131 ms
131 msScripts block the page for only 131 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.1 MB in 122 requests
5.1 MBYour homepage downloads 5.1 MB in 122 requests on a phone: images 4.0 MB (28), scripts 570 KiB (23) and fonts 294 KiB (6). Under 2 MB keeps phones on slow connections fast.
3 images in older formats
3 images (233 KiB) 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 1.4 g of CO₂ per visit
1.44 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.44 g of CO₂e: 172.8 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
Hidden but focusable
1 element hidden from screen readers can still receive keyboard focus.
All page content should be contained by landmarks (5 elements)
All page content should be contained by landmarks: 5 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.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 11 images in the HTML carry an alt attribute.
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 3 failed. 1 more 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.
Title is short (21 characters)
Your title is only 21 characters: “Home - Ghazi Brothers”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“CONSUMER HEALTHCARE” and “CAREERS”). One clear main headline is easier for people and search engines.
8 links crawlers can't follow
8 links have no real href, so search engines can't follow them.
82 internal links, 11 external
The homepage links to 82 pages on ghazibrothers.com and 11 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://ghazibrothers.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://ghazibrothers.com/sitemap.xml.
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://ghazibrothers.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.
1 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.
Other pages
1 linked page is broken
Your homepage links to https://ghazibrothers.com/urdu, which answers with an error. Visitors hit a dead end and search engines drop it.
14 pages without a meta description
https://ghazibrothers.com/ghazi-brothers, https://ghazibrothers.com/vision-values, https://ghazibrothers.com/innovation, https://ghazibrothers.com/sustainability, https://ghazibrothers.com/animal-health and https://ghazibrothers.com/farm-animals and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.
9 pages without an H1
https://ghazibrothers.com/vision-values, https://ghazibrothers.com/innovation, https://ghazibrothers.com/sustainability, https://ghazibrothers.com/animal-health, https://ghazibrothers.com/farm-animals and https://ghazibrothers.com/companion-animals and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 31 found) and read each the way a search engine does.
4 checks passed
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 14 pages that loaded have a <title>.
Best practices
3 small tap targets
3 of 13 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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 ()”.
1 checks passed
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.
Thin social proof
Social proof on the homepage: 1 trust badge. Pairing it with named testimonials or customer logos makes it far more convincing.
Only about 148 words
The homepage has only about 148 words of visible text; thin pages give Google and first-time buyers little to go on.
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 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.
2 checks passed
5 calls to action
The homepage has 5 calls to action, for example “CONTACT”, “GET IN TOUCH” and “Apply Now”.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
3 cookies set on arrival
3Opening the homepage sets 3 cookies (measured from a US location before any click).
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.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
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 ghazibrothers.com, 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
- Analytics
- Google Analytics
- Hosting
- 123net
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on ghazibrothers.com, including 17 speed issues, 4 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.