Website review, no card needed
allcargologistics.com website review
Visit site (opens in a new tab)Reviewed 20 October 202640 issues · 81 checks
This review found 40 issues worth fixing on allcargologistics.com, 19 of them high impact, across 81 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
67DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 1.9 s |
| May 9, 2026 | 1.9 s |
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jun 27, 2026 | 1.8 s |
| Jul 4, 2026 | 1.8 s |
| Jul 11, 2026 | 1.8 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.8 s |
| Aug 8, 2026 | 1.9 s |
| Aug 15, 2026 | 1.9 s |
| Aug 22, 2026 | 1.9 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 12, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Sep 26, 2026 | 1.9 s |
| Oct 3, 2026 | 1.9 s |
| Oct 10, 2026 | 1.9 s |
| Oct 17, 2026 | 1.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 146 ms |
| May 9, 2026 | 146 ms |
| May 16, 2026 | 148 ms |
| May 23, 2026 | 150 ms |
| May 30, 2026 | 152 ms |
| Jun 6, 2026 | 152 ms |
| Jun 13, 2026 | 153 ms |
| Jun 20, 2026 | 153 ms |
| Jun 27, 2026 | 154 ms |
| Jul 4, 2026 | 155 ms |
| Jul 11, 2026 | 154 ms |
| Jul 18, 2026 | 153 ms |
| Jul 25, 2026 | 154 ms |
| Aug 1, 2026 | 154 ms |
| Aug 8, 2026 | 155 ms |
| Aug 15, 2026 | 156 ms |
| Aug 22, 2026 | 155 ms |
| Aug 29, 2026 | 154 ms |
| Sep 5, 2026 | 153 ms |
| Sep 12, 2026 | 152 ms |
| Sep 19, 2026 | 151 ms |
| Sep 26, 2026 | 151 ms |
| Oct 3, 2026 | 151 ms |
| Oct 10, 2026 | 150 ms |
| Oct 17, 2026 | 150 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.5 s
0.9 s
1.4 s
1.9 s
2.3 s
2.8 s
3.3 s
3.7 s
Speed
Use efficient cache lifetimes
12.6 s · 3.7 MB66 files are served with short cache lifetimes, so returning visitors download them again (3.7 MB).
Improve image delivery
6.8 s · 1.5 MB13 images could be 1.5 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.8 s faster on a phone.
Minify JavaScript
1.8 s · 1.0 MB1.0 MB could be saved by minifying JavaScript.
Render-blocking requests
1.1 s1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 1.1 s.
Mobile performance score: 19
19/100Your mobile performance score is 19 (desktop: 45). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 6.0 s
A phone's processor spends 6.0 s on main-thread work while loading, 2.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 773 ms. During a long task the page ignores taps.
Reduce unused JavaScript
542 KiBAbout 542 KiB of JavaScript is downloaded but never used on this page.
Google CDN adds 353 ms
353 msGoogle CDN costs a phone 353 ms of main-thread work and 733 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.
2,360 HTML elements
The page has 2,360 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
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 952 KiB and 486 ms of main-thread time.
Reduce unused CSS
46 KiBAbout 46 KiB of CSS is downloaded but never applied on this page.
Phones get a much slower page than desktops
Desktop scores 45 but mobile only 19. A gap that wide usually means heavy scripts and images that hit phones hardest.
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: 219 ms
219 msYour server sent the HTML in 219 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 CLS: 0.48
0.48For real visitors the layout shifts by 0.48 (75th percentile). Good is under 0.1.
First Contentful Paint: 19.9 s
19.9 sThe first text or image appears after 19.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 28.1 s
28.1 sYour largest element takes 28.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Every Box Sparks a”.
Speed Index: 19.9 s
19.9 sVisually, the page fills in at 19.9 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 39.0 s
39.0 sThe page becomes fully interactive after 39.0 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.367
0.367The layout shifts by 0.367 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Total Blocking Time: 777 ms
777 msScripts block taps and scrolling for 777 ms in total while the page loads. Good is under 200 ms.
Real-user LCP: 3.3 s
3.3 sReal visitors wait 3.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.5 s
2.5 sReal visitors see the first content after 2.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 146 ms to 150 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 1.9 s to 1.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
1 checks passed
Real-user INP: 139 ms
139 msReal visitors wait 139 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Images and page weight
Page weight: 8.2 MB in 80 requests
8.2 MBYour homepage downloads 8.2 MB in 80 requests on a phone: HTML 3.1 MB (2), images 2.6 MB (22) and scripts 2.2 MB (43). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
WQpxBdsFK9wXCYsf4Oid.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
7 images in older formats
7 images (764 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.
5 images below the first screen load straight away
5 images further down the page (417 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.3 g of CO₂ per visit
2.32 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.32 g of CO₂e: 278.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
Scrollable region must have keyboard access (4 elements)
Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.
1 text element with low contrast
1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
2 checks passed
Every image has alt text
All 97 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 3 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (18 characters)
Your title is only 18 characters: “Allcargo Logistics”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is short (23 characters)
Your meta description is only 23 characters: “Allcargo Logistics Home”. 70 to 160 characters is enough to sell the click.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.
130 internal links, 7 external
The homepage links to 130 pages on allcargologistics.com and 7 external pages.
5 checks passed
One H1 headline
Your main headline reads: “AllcargoGATI: India's Premier Express Distribution and Supply Chain Solutions”.
Canonical URL set
The canonical URL is https://www.allcargologistics.com/.
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.
XML sitemap found
Your XML sitemap is reachable at https://www.allcargologistics.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://www.allcargologistics.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,872 words), so crawlers that don't run JavaScript still read it.
Other pages
7 pages without a title
https://www.allcargologistics.com/insights/news-press-releases/the-rush-behind-the-rush-how-india-s-supply-chains-keeps-up-with-the-festive-surge, https://www.allcargologistics.com/insights/news-press-releases/is-connectivity-key-to-logistics-competitiveness, https://www.allcargologistics.com/insights/news-press-releases/why-multimodal-logistics-will-drive-india-s-next-phase-of-growth, https://www.allcargologistics.com/insights/news-press-releases/avashya-foundation-honours-the-families-of-india-s-martyrs, https://www.allcargologistics.com/insights/news-press-releases/allcargo-logistics-strengthening-supply-chain-frameworks-for-fmcg-players and https://www.allcargologistics.com/insights/news-press-releases/allcargo-logistics-strengthens-varanasi-handloom-cluster-with-secure-door-to-door-and-cod-services and 1 other have no <title>, so Google invents the link text in results.
7 pages share a meta description
https://www.allcargologistics.com/insights/news-press-releases/the-rush-behind-the-rush-how-india-s-supply-chains-keeps-up-with-the-festive-surge, https://www.allcargologistics.com/insights/news-press-releases/is-connectivity-key-to-logistics-competitiveness, https://www.allcargologistics.com/insights/news-press-releases/why-multimodal-logistics-will-drive-india-s-next-phase-of-growth, https://www.allcargologistics.com/insights/news-press-releases/avashya-foundation-honours-the-families-of-india-s-martyrs, https://www.allcargologistics.com/insights/news-press-releases/allcargo-logistics-strengthening-supply-chain-frameworks-for-fmcg-players and https://www.allcargologistics.com/insights/news-press-releases/allcargo-logistics-strengthens-varanasi-handloom-cluster-with-secure-door-to-door-and-cod-services and 1 other use the same meta description. A description written for each page earns more clicks.
15 links to non-canonical URLs
Your homepage links to 15 pages by a URL that isn't their canonical one, for example https://www.allcargologistics.com/express-logistics/express-surface, whose canonical is //express-logistics/express-surface. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 113 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
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.
Best practices
5 small tap targets
5 of 17 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://www.clarity.ms/tag/ybvxv7oooj' violates the following Content Security Policy directive: "s…”.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 2,964 words of copy
The homepage carries about 2,964 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Book”.
6 calls to action
The homepage has 6 calls to action, for example “Contact Us”, “Book Pickup” and “Ecommerce Order Fulfillment”.
2 short forms
2 short forms (4 fields at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 1 phone link and 0 email links.
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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
2 cookies set on arrival
2Opening 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.
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 allcargologistics.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Angular
- Analytics
- Google Analytics | Microsoft Clarity
Company
- Founded
- 1993
- Headquarters
- Mumbai
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 allcargologistics.com, including 21 speed issues, 3 SEO issues and 1 conversion gap. 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.