Website review, no card needed
neopac.in website review
Visit site (opens in a new tab)Reviewed 24 October 202643 issues · 87 checks
This review found 43 issues worth fixing on neopac.in, 15 of them high impact, across 87 checks. The most urgent: improve image delivery. 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
65DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.4 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.2 s |
| Jul 25, 2026 | 3.3 s |
| Aug 1, 2026 | 3.2 s |
| Aug 8, 2026 | 3.3 s |
| Aug 15, 2026 | 3.4 s |
| Aug 22, 2026 | 3.4 s |
| Aug 29, 2026 | 3.6 s |
| Sep 5, 2026 | 3.4 s |
| Oct 3, 2026 | 3.3 s |
| Oct 10, 2026 | 3.4 s |
| Oct 17, 2026 | 3.3 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| Jun 13, 2026 | 94 ms |
| Jun 20, 2026 | 94 ms |
| Jun 27, 2026 | 85 ms |
| Jul 4, 2026 | 89 ms |
| Jul 18, 2026 | 90 ms |
| Aug 1, 2026 | 86 ms |
| Aug 8, 2026 | 85 ms |
| Aug 15, 2026 | 85 ms |
| Aug 22, 2026 | 83 ms |
| Oct 3, 2026 | 82 ms |
| Oct 10, 2026 | 84 ms |
| Oct 17, 2026 | 83 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
Improve image delivery
6.4 s · 2.9 MB17 images could be 2.9 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 6.4 s faster on a phone.
Reduce unused JavaScript
3.8 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.8 s faster on a phone.
Use efficient cache lifetimes
2.4 s · 661 KiB54 files are served with short cache lifetimes, so returning visitors download them again (661 KiB).
Render-blocking requests
1.4 s3 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 48
48/100Your mobile performance score is 48 (desktop: 79). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
6 third-party services on the page
6 third-party services load with your homepage (Google Maps, Google CDN and Google Tag Manager and others), adding 2.7 MB and 1.2 s of main-thread time.
Google Maps adds 585 ms
585 msGoogle Maps costs a phone 585 ms of main-thread work and 1.4 MB 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.
Reduce unused CSS
600 ms · 129 KiBAbout 129 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Font display
700 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 700 ms).
Google CDN adds 375 ms
375 msGoogle CDN costs a phone 375 ms of main-thread work and 731 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.
Main-thread work: 3.2 s
A phone's processor spends 3.2 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 223 ms
223 msGoogle Tag Manager costs a phone 223 ms of main-thread work and 477 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 170 ms. During a long task the page ignores taps.
Phones get a much slower page than desktops
Desktop scores 79 but mobile only 48. 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.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 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.
Largest Contentful Paint: 25.1 s
25.1 sYour largest element takes 25.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SPRINGTube Oval® Designed to Maximize Your Brand’s Impact R…”.
Time to Interactive: 26.3 s
26.3 sThe page becomes fully interactive after 26.3 s. Good is under 3.8 s.
Speed Index: 8.2 s
8.2 sVisually, the page fills in at 8.2 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.277
0.277The layout shifts by 0.277 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user CLS: 0.14
0.14For real visitors the layout shifts by 0.14 (75th percentile). Good is under 0.1.
Real-user FCP: 2.9 s
2.9 sReal visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.
37 images without width and height
37 images have no width and height attributes, so the layout jumps as each one loads.
Total Blocking Time: 230 ms
230 msScripts block taps and scrolling for 230 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.4 s to 3.3 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
2 checks passed
Tap response (INP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 94 ms to 83 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 1.7 s
1.7 sThe first text or image appears after 1.7 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 7.7 MB in 115 requests
7.7 MBYour homepage downloads 7.7 MB in 115 requests on a phone: images 4.4 MB (38), scripts 2.6 MB (53) and other files 359 KiB (12). Under 2 MB keeps phones on slow connections fast.
12 images in older formats
12 images (2.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.
15 images below the first screen load straight away
15 images further down the page (2.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
244 KiB1 image is downloaded at several times the size a phone draws it, for example cholayil-logo.png at 1,634 px wide, shown at 175 px. Resized copies would save about 244 KiB.
About 2.2 g of CO₂ per visit
2.18 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.18 g of CO₂e: 261.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
3 text elements with low contrast
3 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Frames without titles
3 frames have no title, so screen-reader users cannot tell what they contain.
Links look like plain text
1 link inside paragraphs relies on colour alone to stand out.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (13 elements)
All page content should be contained by landmarks: 13 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.
5 links without text
5 visible links have no text or label, so screen readers cannot say where they go.
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 → h4, h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 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
Title is short (19 characters)
Your title is only 19 characters: “Home - Neopac India”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is short (35 characters)
Your meta description is only 35 characters: “Plastic and Laminate Tube Packaging”. 70 to 160 characters is enough to sell the click.
4 H1 headlines
There are 4 <h1> headlines (“SPRINGTube Oval®Designed to Maximize Your Brand’s…”, “PaperXSave plastics with fibre-based tube packagi…” and “SPRINGTUBE®Limitless Decoration and Eco-Friendly”). One clear main headline is easier for people and search engines.
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.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
34 internal links, 15 external
The homepage links to 34 pages on neopac.in and 15 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.neopac.in/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, WebPage and WebSite.
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.neopac.in/sitemap_index.xml.
AI search readiness
No llms.txt
There is no https://www.neopac.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.
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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (1,254 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages share a meta description
https://www.neopac.in/why-neopac, https://www.neopac.in/sustainability, https://www.neopac.in/paperx, https://www.neopac.in/coex-pcr-tube, https://www.neopac.in/light-weight-coex and https://www.neopac.in/pblmono and 9 others use the same meta description. A description written for each page earns more clicks.
5 pages without an H1
https://www.neopac.in/contact-us, https://www.neopac.in/career, https://www.neopac.in/at-cmpl-expo-in-mumbai-3d-neopac-to-introduce-tubes-with-locally-sourced-pcr-content, https://www.neopac.in/neopac-celebrates-double-victory-at-ifca-star-awards-2025 and https://www.neopac.in/neopac-india-wins-double-honor-at-the-2025-fipsa-awards have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 18 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 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
20 of 22 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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,121 words of copy
The homepage carries about 1,121 words of visible text.
7 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT”.
6 calls to action
The homepage has 6 calls to action, for example “[email protected]”, “Contact” and “Contact Us”.
1 short form
A short form (1 field at most) is right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 1 testimonial or review block and 5 trust badges.
Analytics in place
Analytics detected: Google Tag Manager, Google Analytics and LinkedIn Insight.
Direct contact links
Visitors can reach you directly: 2 phone links and 2 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight (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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
9 other companies contacted
Loading the homepage contacts 9 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 neopac.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
- Analytics
- Google Analytics | Google Tag Manager
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on neopac.in, including 21 speed issues, 5 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.