Website review, no card needed
jaffer.com website review
Visit site (opens in a new tab)Reviewed 1 November 202640 issues · 84 checks
This review found 40 issues worth fixing on jaffer.com, 17 of them high impact, across 84 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
62DClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
25.9 s · 12.1 MB110 files are served with short cache lifetimes, so returning visitors download them again (12.1 MB).
Improve image delivery
17.8 s · 7.3 MB64 images could be 7.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 17.8 s faster on a phone.
Render-blocking requests
1.4 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 42
42/100Your mobile performance score is 42. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused JavaScript
630 ms · 144 KiBAbout 144 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 630 ms faster on a phone.
4 third-party services on the page
4 third-party services load with your homepage (Facebook, Google Tag Manager and Google Analytics and others), adding 566 KiB and 289 ms of main-thread time.
Minify JavaScript
160 ms · 15 KiB15 KiB could be saved by minifying JavaScript.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 112 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
45 KiBAbout 45 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
13 KiBPolyfills for old browsers add 13 KiB JavaScript that modern phones do not need.
Minify CSS
8 KiB8 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.
2 checks passed
Main-thread work: 0.9 s
A phone's processor spends 0.9 s on main-thread work while loading, 370 ms of it running JavaScript. That is comfortably low.
Server response: 2 ms
2 msYour server sent the HTML in 2 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 36.7 s
36.7 sYour largest element takes 36.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Machinery”.
Time to Interactive: 37.2 s
37.2 sThe page becomes fully interactive after 37.2 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.659
0.659The layout shifts by 0.659 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Speed Index: 7.7 s
7.7 sVisually, the page fills in at 7.7 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 1.8 s
1.8 sThe first text or image appears after 1.8 s on a phone. Good is under 1.8 s.
8 images without width and height
8 images have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Total Blocking Time: 151 ms
151 msScripts block the page for only 151 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 12.5 MB in 117 requests
12.5 MBYour homepage downloads 12.5 MB in 117 requests on a phone: images 11.8 MB (94), scripts 498 KiB (11) and fonts 147 KiB (1). Under 2 MB keeps phones on slow connections fast.
6 images over 500 KB
6 images weigh 8.4 MB together. On a phone connection a single image that size takes seconds.
3 images far larger than shown
1.7 MB3 images are downloaded at several times the size a phone draws them, for example slide1png_11426.png at 1,920 px wide, shown at 390 px. Resized copies would save about 1.7 MB.
23 images in older formats
23 images (10.7 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.
25 images below the first screen load straight away
25 images further down the page (4.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.5 g of CO₂ per visit
3.54 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.54 g of CO₂e: 424.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Certain ARIA roles must contain particular children (1 element)
Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Links look like plain text
3 links inside paragraphs rely on colour alone to stand out.
ARIA input fields must have an accessible name (1 element)
ARIA input fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.
64 images without alt text
64 images have no alt text, which hurts accessibility and image search.
116 links without text
116 visible links have no text or label, so screen readers cannot say where they go.
All page content should be contained by landmarks (12 elements)
All page content should be contained by landmarks: 12 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.
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 (h1 → h3, h1 → h4 and h1 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
30 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 30 passed and 10 failed. 1 more need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (25 characters)
Your title is only 25 characters: “Jaffer Group of Companies”. Between 30 and 65 characters leaves room to say what you do and for whom.
6 H1 headlines
There are 6 <h1> headlines (“Our Businesses”, “News & Events” and “Videos”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
Meta description is long (463 characters)
Your meta description is 463 characters; Google truncates after about 160, so the end of your pitch is cut.
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.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
46 internal links, 64 external
The homepage links to 46 pages on jaffer.com and 64 external pages.
3 checks passed
Structured data in place
Structured data found: Organization.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://jaffer.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://jaffer.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.
3 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.
Organization data: 5 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (501 words), so crawlers that don't run JavaScript still read it.
Other pages
15 internal pages checked
We fetched 15 pages linked from your homepage (of 24 found) and read each the way a search engine does.
7 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.
Every page has an H1
Each page we checked has a main headline.
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
119 distorted images
119 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “gtag is not defined”.
2 checks passed
Tap targets are thumb-sized
11 of 11 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.
Local business without LocalBusiness data
Your homepage shows a street address 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.
Thin social proof
Social proof on the homepage: 58 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
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 map or directions link
There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.
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 440 words of copy
The homepage carries about 440 words of visible text.
3 checks passed
1 call to action
The homepage has 1 call to action, for example “Contact”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and 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.
6 cookies set on arrival
6Opening the homepage sets 6 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.
5 other companies contacted
Loading the homepage contacts 5 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 jaffer.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
- The footer still says © 2021.
Stack
- Framework
- jQuery
- Analytics
- Google Analytics
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on jaffer.com, including 11 speed issues, 6 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.