Website review, no card needed
gangesintl.com website review
Visit site (opens in a new tab)Reviewed 18 November 202641 issues · 79 checks
This review found 41 issues worth fixing on gangesintl.com, 15 of them high impact, across 79 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
73CClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
Speed
Use efficient cache lifetimes
14.3 s · 12.2 MB92 files are served with short cache lifetimes, so returning visitors download them again (12.2 MB).
Improve image delivery
2.7 s · 5.3 MB52 images could be 5.3 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.7 s faster on a phone.
Render-blocking requests
2.6 s6 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.6 s.
Reduce unused JavaScript
1.8 s · 416 KiBAbout 416 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.8 s faster on a phone.
Reduce unused CSS
1.5 s · 256 KiBAbout 256 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Font display
1.4 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.4 s).
Mobile performance score: 54
54/100Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.
Google Tag Manager adds 262 ms
262 msGoogle Tag Manager costs a phone 262 ms of main-thread work and 519 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.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, FontAwesome CDN and Google Fonts and others), adding 709 KiB and 265 ms of main-thread time.
Minify JavaScript
150 ms · 35 KiB35 KiB could be saved by minifying JavaScript.
Minify CSS
150 ms · 20 KiB20 KiB could be saved by minifying CSS.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 146 ms. During a long task the page ignores taps.
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, 255 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: 26.7 s
26.7 sYour largest element takes 26.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Livestock Equipments | 5G Technology Tower | 5G Towers | 5G…”.
Time to Interactive: 27.3 s
27.3 sThe page becomes fully interactive after 27.3 s. Good is under 3.8 s.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Speed Index: 5.7 s
5.7 sVisually, the page fills in at 5.7 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.213
0.213The layout shifts by 0.213 while loading, so content jumps under the reader's thumb. Good is under 0.1.
15 images without width and height
15 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: 60 ms
60 msScripts block the page for only 60 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 12.9 MB in 106 requests
12.9 MBYour homepage downloads 12.9 MB in 106 requests on a phone: images 10.9 MB (77), fonts 987 KiB (10) and scripts 804 KiB (10). Under 2 MB keeps phones on slow connections fast.
6 images over 500 KB
6 images weigh 7.4 MB together. On a phone connection a single image that size takes seconds.
4 images far larger than shown
2.0 MB4 images are downloaded at several times the size a phone draws them, for example Gallery2_nOstttm_ky1wTGu.png at 1,352 px wide, shown at 350 px. Resized copies would save about 2.0 MB.
21 images in older formats
21 images (9.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.
26 images below the first screen load straight away
26 images further down the page (4.6 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 3.7 g of CO₂ per visit
3.66 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.66 g of CO₂e: 438.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
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.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (4 elements)
ARIA role should be appropriate for the element: 4 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (4 elements)
Elements marked as presentational should be consistently ignored: 4 elements on the page fail this check, rated minor by axe-core.
Headings skip levels
Headings skip levels (h3 → h5, h1 → h5 and h1 → h4), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 77 images in the HTML carry an alt attribute.
35 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: 35 passed and 8 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (67 characters)
Your title is 67 characters, so Google will cut it off around 60: “Ganges Internationale | Telecom Towers | Scaffolding systems | CRFS”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 H1 headlines
There are 3 <h1> headlines (“Livestock Equipments”, “Ringlock Scaffolding Systems” and “One of The Leading Telecom Tower Manufacturers fr…”). One clear main headline is easier for people and search engines.
Meta description is long (183 characters)
Your meta description is 183 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.
No XML sitemap
No XML sitemap at https://gangesintl.com/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at gangesintl.com/robots.txt, the first file search crawlers ask for.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
70 internal links, 7 external
The homepage links to 70 pages on gangesintl.com and 7 external pages.
1 checks passed
Canonical URL set
The canonical URL is https://www.gangesintl.com/.
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://gangesintl.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
There is no robots.txt, so nothing stops the crawlers behind ChatGPT search, Claude and Perplexity from reading the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (572 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share 2 titles
https://gangesintl.com/mission_vision_values and https://gangesintl.com/testing_facility all use the title “Mission vision values | Telecom Tower Manufacturer | TLT | Ganges”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages share a meta description
https://gangesintl.com/mission_vision_values and https://gangesintl.com/testing_facility use the same meta description. A description written for each page earns more clicks.
2 links to non-canonical URLs
Your homepage links to 2 pages by a URL that isn't their canonical one, for example https://gangesintl.com/manufacturing_facility, whose canonical is https://gangesintl.com/scaffolding_systems. 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 24 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.
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
7 small tap targets
7 of 15 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
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
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.
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 355 words of copy
The homepage carries about 355 words of visible text.
5 checks passed
4 calls to action
The homepage has 4 calls to action, for example “Contact Us” and “Get Started”.
5 short forms
5 short forms (2 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 30 customer or partner logos and 4 trust badges.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
3 trackers load before any consent
3Before 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.
3 cookies set on arrival
3Opening the homepage sets 3 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.
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.
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 gangesintl.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 © 2024.
Stack
- Framework
- jQuery
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- AWS
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 41 issues on gangesintl.com, including 14 speed issues, 8 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.