Website review, no card needed
cosco.in website review
Visit site (opens in a new tab)Reviewed 20 October 202642 issues · 86 checks
This review found 42 issues worth fixing on cosco.in, 16 of them high impact, across 86 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
63DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jun 13, 2026 | 3.5 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.7 s |
| Jul 4, 2026 | 3.6 s |
| Jul 11, 2026 | 3.6 s |
| Jul 18, 2026 | 3.6 s |
| Jul 25, 2026 | 3.8 s |
| Aug 1, 2026 | 4.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jun 13, 2026 | 105 ms |
| Jun 20, 2026 | 99 ms |
| Jun 27, 2026 | 105 ms |
| Jul 4, 2026 | 107 ms |
| Jul 11, 2026 | 105 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
Speed
Use efficient cache lifetimes
1.6 s · 3.9 MB90 files are served with short cache lifetimes, so returning visitors download them again (3.9 MB).
Render-blocking requests
2.1 s15 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Mobile performance score: 39
39/100Your mobile performance score is 39 (desktop: 50). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
5.0 MB36 images could be 5.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Reduce unused JavaScript
450 ms · 88 KiBAbout 88 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.
Reduce unused CSS
300 ms · 67 KiBAbout 67 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Minify JavaScript
300 ms · 47 KiB47 KiB could be saved by minifying JavaScript.
2,867 HTML elements
The page has 2,867 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify CSS
150 ms · 13 KiB13 KiB could be saved by minifying CSS.
5 third-party services on the page
5 third-party services load with your homepage (jQuery CDN, Cloudflare CDN and Bootstrap CDN and others), adding 150 KiB and 124 ms of main-thread time.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 62 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).
Legacy JavaScript
9 KiBPolyfills for old browsers add 9 KiB JavaScript that modern phones do not need.
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.
2 checks passed
Main-thread work: 0.7 s
A phone's processor spends 0.7 s on main-thread work while loading, 178 ms of it running JavaScript. That is comfortably low.
Server response: 17 ms
17 msYour server sent the HTML in 17 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 16.7 s
16.7 sYour largest element takes 16.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Cosco Sports Fitness”.
Speed Index: 14.4 s
14.4 sVisually, the page fills in at 14.4 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 17.7 s
17.7 sThe page becomes fully interactive after 17.7 s. Good is under 3.8 s.
Cumulative Layout Shift: 0.791
0.791The layout shifts by 0.791 while loading, so content jumps under the reader's thumb. Good is under 0.1.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 105 ms to 105 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.5 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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: 6 ms
6 msScripts block the page for only 6 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 9.8 MB in 98 requests
9.8 MBYour homepage downloads 9.8 MB in 98 requests on a phone: images 9.4 MB (63), scripts 220 KiB (16) and stylesheets 101 KiB (16). Under 2 MB keeps phones on slow connections fast.
5 images over 500 KB
5 images weigh 3.0 MB together. On a phone connection a single image that size takes seconds.
34 images in older formats
34 images (9.1 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.
2 images far larger than shown
108 KiB2 images are downloaded at several times the size a phone draws them, for example instagram.png at 835 px wide, shown at 35 px. Resized copies would save about 108 KiB.
4 images below the first screen load straight away
4 images further down the page (160 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.8 g of CO₂ per visit
2.78 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.78 g of CO₂e: 333.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
43 text elements with low contrast
43 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
Hidden but focusable
4 elements hidden from screen readers can still receive keyboard focus.
13 images without alt text
13 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (18 elements)
All page content should be contained by landmarks: 18 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.
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.
7 links without text
7 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
35 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 44 WCAG 2.2 A/AA and best-practice rules on the phone render: 35 passed and 9 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
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 (175 characters)
Your meta description is 175 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 2 problems
Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: missing name”.
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://cosco.in/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at cosco.in/robots.txt, the first file search crawlers ask for.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
389 internal links, 14 external
The homepage links to 389 pages on cosco.in and 14 external pages.
1 checks passed
Title: 54 characters
Your title is a healthy 54 characters: “Cosco Sports Equipment | Cosco Fitness Equipment India”.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing name, url and description. 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://cosco.in/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 (1,442 words), so crawlers that don't run JavaScript still read it.
Other pages
12 pages slow to respond
https://cosco.in/products/india/accessories-3/strength-2, https://cosco.in/products/india/accessories-3/training-7, https://cosco.in/products/india/accessories-3/yoga, https://cosco.in/products/india/badminton/grips, https://cosco.in/products/india/badminton/nets-2 and https://cosco.in/products/india/badminton/racquets and 6 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 185 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
1 broken image
1 image failed to load on a phone, for example https://www.cosco.in/uploads/ckeditor/images/about.jpg.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://www.cosco.in/assets/theme/css/style.css' from origin 'https://cosco.in' has been b…”.
15 distorted images
15 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
239 of 240 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 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,059 words of copy
The homepage carries about 1,059 words of visible text.
3 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Contact for Investors” and “Contact Us”.
6 calls to action
The homepage has 6 calls to action, for example “Contact for Investors”, “Contact Us” and “Shop Now”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (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.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 cosco.in, 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
Company
- Founded
- 1980
- Headquarters
- Delhi
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on cosco.in, including 14 speed issues, 7 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.