Website review, no card needed

manshabrothers.com logo

manshabrothers.com website review

Visit site (opens in a new tab)Reviewed 2 November 202634 issues · 79 checks

This review found 34 issues worth fixing on manshabrothers.com, 12 of them high impact, across 79 checks. The most urgent: google CDN adds 1.5 s. 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
5.4 s4.6 sJul 25Oct 314.9 s
Show as table
DateReal-visitor load time (LCP)
Jul 25, 20265.0 s
Aug 1, 20265.0 s
Aug 8, 20265.0 s
Aug 15, 20265.0 s
Aug 22, 20265.1 s
Aug 29, 20265.1 s
Sep 5, 20265.2 s
Sep 12, 20265.2 s
Sep 19, 20265.2 s
Sep 26, 20265.3 s
Oct 3, 20264.7 s
Oct 10, 20264.9 s
Oct 17, 20264.9 s
Oct 24, 20264.7 s
Oct 31, 20264.9 s

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 manshabrothers.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. manshabrothers.com at 1.0 s1.0 s
  2. manshabrothers.com at 2.1 s2.1 s
  3. manshabrothers.com at 3.1 s3.1 s
  4. manshabrothers.com at 4.1 s4.1 s
  5. manshabrothers.com at 5.2 s5.2 s
  6. manshabrothers.com at 6.2 s6.2 s
  7. manshabrothers.com at 7.2 s7.2 s
  8. manshabrothers.com at 8.3 s8.3 s

Speed

11 to fix55
  • Google CDN adds 1.5 s

    1.5 s

    Google CDN costs a phone 1.5 s of main-thread work and 1.1 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.

  • Render-blocking requests

    1.6 s

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

  • Main-thread work: 7.5 s

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

  • 5 third-party services on the page

    5 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1.5 MB and 2.0 s of main-thread time.

  • Mobile performance score: 55

    55/100

    Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.

  • Reduce initial server response time

    708 ms

    Reduce initial server response time. Google estimates savings of 708 ms on a phone.

  • Document request latency

    700 ms

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

  • Reduce unused JavaScript

    646 KiB

    About 646 KiB of JavaScript is downloaded but never used on this page.

  • 20 long tasks on the main thread

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

  • Google Tag Manager adds 321 ms

    321 ms

    Google Tag Manager costs a phone 321 ms of main-thread work and 167 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.

  • Server response: 808 ms

    808 ms

    Your server takes 808 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.

  • Use efficient cache lifetimes

    46 KiB

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

  • Reduce unused CSS

    33 KiB

    About 33 KiB of CSS is downloaded but never applied on this page.

  • Improve image delivery

    14 KiB

    2 images could be 14 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 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.

Core Web Vitals

9 to fix50
  • 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: 4.9 s

    4.9 s

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

  • Real-user FCP: 4.1 s

    4.1 s

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

  • Real-user TTFB: 2.7 s

    2.7 s

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

  • Total Blocking Time: 2.9 s

    2.9 s

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

  • Time to Interactive: 14.2 s

    14.2 s

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

  • Speed Index: 9.2 s

    9.2 s

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

  • Largest Contentful Paint: 3.1 s

    3.1 s

    Your largest element takes 3.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Since 1989 30+ Service Centers Nationwide 24/7 After-Sales …”. Most of its time is resource load delay (3.6 s).

  • 21 images without width and height

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

  • Largest content (LCP) held steady for real visitors

    -4%

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

3 checks passed
  • Real-user CLS: 0.01

    0.01

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

  • First Contentful Paint: 1.8 s

    1.8 s

    The first text or image appears after 1.8 s, inside the 1.8 s “good” threshold.

  • Cumulative Layout Shift: 0.003

    0.003

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

Images and page weight

1 to fix85
  • Page weight: 2.7 MB in 117 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 117 requests on a phone: scripts 1.4 MB (33), other files 696 KiB (4) and images 212 KiB (40). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (26 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 0.8 g of CO₂ per visit

    0.76 g

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

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9696
  • 4 text elements with low contrast

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    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)

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

  • 2 form fields without a label

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

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 51 images in the HTML carry an alt attribute.

  • 51 automated accessibility rules passed

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

SEO

5 to fixGoogle 9272
  • No H1 headline

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

  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Mansha Brothers | ICT, Automation & Technology Solutions in Pakistan”.

  • Meta description is long (165 characters)

    Your meta description is 165 characters; Google truncates after about 160, so the end of your pitch is cut.

  • No XML sitemap

    No XML sitemap at https://manshabrothers.com/sitemap_index.xml, so Google discovers your pages only by following links.

  • 8 links with vague text

    8 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

  • 107 internal links, 3 external

    The homepage links to 107 pages on manshabrothers.com and 3 external pages.

4 checks passed
  • Canonical URL set

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

  • Structured data in place

    Structured data found: Article, ImageObject, Organization, Person and WebPage.

  • 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 and points crawlers to your sitemap.

AI search readiness

1 to fix88
  • Organization data is thin (3 of 6 facts)

    Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

  • No llms.txt

    There is no https://manshabrothers.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 (1,641 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 7 pages without an H1

    https://manshabrothers.com/about-us, https://manshabrothers.com/our-clients, https://manshabrothers.com/partners, https://manshabrothers.com/solutions, https://manshabrothers.com/case-studies and https://manshabrothers.com/case-studies/lipton-pakistan-hdl-automation-deployment and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

  • 15 pages slow to respond

    https://manshabrothers.com/about-us, https://manshabrothers.com/our-clients, https://manshabrothers.com/partners, https://manshabrothers.com/solutions, https://manshabrothers.com/solutions/security-surveillance and https://manshabrothers.com/solutions/audio-visual-solutions 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 22 found) and read each the way a search engine does.

6 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.

  • Every page has a meta description

    All 15 pages that loaded have a meta description.

  • 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

1 to fixGoogle 9693
  • 13 small tap targets

    13 of 16 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

100
  • 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,443 words of copy

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

6 checks passed
  • Clear next step on the first screen

    On a phone, the first screen shows a clear next step: “Talk to Sales” and “Request a Quote”.

  • 18 calls to action

    The homepage has 18 calls to action, for example “Contact”, “Talk to Sales” and “Request a Quote”.

  • 3 short forms

    3 short forms (7 fields at most) are right on the homepage, asking for an email.

  • Social proof on the page

    Social proof on the homepage: 139 testimonial or review blocks, 7 trust badges and “0 + Clients”.

  • Analytics in place

    Analytics detected: Google Analytics.

  • Direct contact links

    Visitors can reach you directly: 5 phone links and 3 email links.

Privacy and tracking

1 to fix
  • 3 trackers load before any consent

    3

    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.

  • 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.

  • 7 other companies contacted

    Loading the homepage contacts 7 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 manshabrothers.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
Interserver, Inc

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 manshabrothers.com, including 20 speed issues and 5 SEO issues. 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