Website review, no card needed
epack.in website review
Visit site (opens in a new tab)Reviewed 27 October 202634 issues · 84 checks
This review found 34 issues worth fixing on epack.in, 10 of them high impact, across 84 checks. The most urgent: render-blocking requests. 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 4.6 s |
| May 16, 2026 | 4.6 s |
| May 23, 2026 | 4.6 s |
| May 30, 2026 | 4.6 s |
| Jun 6, 2026 | 4.6 s |
| Jun 13, 2026 | 4.6 s |
| Jun 20, 2026 | 4.5 s |
| Jun 27, 2026 | 4.5 s |
| Jul 4, 2026 | 4.5 s |
| Jul 11, 2026 | 4.5 s |
| Jul 18, 2026 | 4.6 s |
| Jul 25, 2026 | 4.8 s |
| Aug 1, 2026 | 4.9 s |
| Aug 8, 2026 | 5.1 s |
| Aug 15, 2026 | 5.1 s |
| Aug 22, 2026 | 6.0 s |
| Aug 29, 2026 | 6.0 s |
| Sep 5, 2026 | 6.0 s |
| Sep 12, 2026 | 6.0 s |
| Sep 19, 2026 | 5.5 s |
| Sep 26, 2026 | 5.4 s |
| Oct 3, 2026 | 5.0 s |
| Oct 10, 2026 | 4.4 s |
| Oct 17, 2026 | 3.6 s |
| Oct 24, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 127 ms |
| May 16, 2026 | 125 ms |
| May 23, 2026 | 127 ms |
| May 30, 2026 | 127 ms |
| Jun 6, 2026 | 129 ms |
| Jun 13, 2026 | 129 ms |
| Jun 20, 2026 | 128 ms |
| Jun 27, 2026 | 125 ms |
| Jul 4, 2026 | 123 ms |
| Jul 11, 2026 | 123 ms |
| Jul 18, 2026 | 122 ms |
| Jul 25, 2026 | 122 ms |
| Aug 1, 2026 | 122 ms |
| Aug 8, 2026 | 122 ms |
| Aug 15, 2026 | 124 ms |
| Aug 22, 2026 | 153 ms |
| Aug 29, 2026 | 157 ms |
| Sep 5, 2026 | 161 ms |
| Sep 12, 2026 | 162 ms |
| Sep 19, 2026 | 138 ms |
| Sep 26, 2026 | 139 ms |
| Oct 3, 2026 | 139 ms |
| Oct 10, 2026 | 139 ms |
| Oct 17, 2026 | 143 ms |
| Oct 24, 2026 | 146 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
Render-blocking requests
2.1 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.1 s.
Mobile performance score: 49
49/100Your mobile performance score is 49 (desktop: 59). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused JavaScript
750 ms · 410 KiBAbout 410 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 971 KiB and 976 ms of main-thread time.
Document request latency
700 ms · 89 KiBThe HTML itself could arrive about 700 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce unused CSS
600 ms · 108 KiBAbout 108 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.
Reduce initial server response time
698 msReduce initial server response time. Google estimates savings of 698 ms on a phone.
Google Tag Manager adds 625 ms
625 msGoogle Tag Manager costs a phone 625 ms of main-thread work and 524 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.9 s
A phone's processor spends 3.9 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 319 ms. During a long task the page ignores taps.
1,522 HTML elements
The page has 1,522 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Server response: 798 ms
798 msYour server takes 798 ms to send the HTML. Google recommends under 600 ms; everything else waits for it.
Use efficient cache lifetimes
210 KiB4 files are served with short cache lifetimes, so returning visitors download them again (210 KiB).
Improve image delivery
198 KiB8 images could be 198 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
150 ms · 5 KiB5 KiB could be saved by minifying JavaScript.
Legacy JavaScript
12 KiBPolyfills for old browsers add 12 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.
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: 13.4 s
13.4 sYour largest element takes 13.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PRE ENGINEERED & PREFABRICATED BUILDING SOLUTIONS At EPACK …”.
Speed Index: 14.8 s
14.8 sVisually, the page fills in at 14.8 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 20.5 s
20.5 sThe page becomes fully interactive after 20.5 s. Good is under 3.8 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Real-user LCP: 3.4 s
3.4 sReal visitors wait 3.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.5 s
1.5 sReal visitors wait 1.5 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 425 ms
425 msScripts block taps and scrolling for 425 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 15% slower for real visitors
+15%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 127 ms to 146 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 151 ms
151 msReal visitors wait 151 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Largest content (LCP) got 28% faster for real visitors
-28%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 4.6 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.065
0.065The layout barely moves while loading (CLS 0.065, good is under 0.1).
Images and page weight
Page weight: 3.7 MB in 168 requests
3.7 MBYour homepage downloads 3.7 MB in 168 requests on a phone: images 2.0 MB (103), scripts 1.2 MB (25) and fonts 174 KiB (7). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Golden-Book-World-Record-390x156.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).
12 images below the first screen load straight away
12 images further down the page (454 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image far larger than shown
113 KiB1 image is downloaded at several times the size a phone draws it, for example Footer-Icons.webp at 2,000 px wide, shown at 366 px. Resized copies would save about 113 KiB.
About 1.0 g of CO₂ per visit
1.04 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.04 g of CO₂e: 124.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
Hidden but focusable
6 elements hidden from screen readers can still receive keyboard focus.
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.
Links look like plain text
2 links inside paragraphs rely on colour alone to stand out.
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.
6 links without text
6 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (4 elements).
2 checks passed
Every image has alt text
All 98 images in the HTML carry an alt attribute.
48 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: 48 passed and 4 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
131 internal links, 13 external
The homepage links to 131 pages on epack.in and 13 external pages.
8 checks passed
Meta description: 149 characters
Your meta description is 149 characters: “Discover EPACK Prefab’s modular PEB, LGSF, sandwich panel & porta cabin solutions—turnkey construction delivered across…”.
One H1 headline
Your main headline reads: “PRE ENGINEERED & PREFABRICATED BUILDING SOLUTIONS”.
Title: 61 characters
Your title is a healthy 61 characters: “EPACK Prefab: Prefabricated Buildings, PEBs & Sandwich Panels”.
Canonical URL set
The canonical URL is https://www.epack.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.epack.in/sitemap_index.xml.
AI search readiness
4 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,098 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.epack.in/llms.txt (9 KiB, 98 links), a plain-text guide to the site for AI tools.
Other pages
9 pages slow to respond
https://www.epack.in/product-services, https://www.epack.in/pre-engineered-building, https://www.epack.in/warehouse-godown, https://www.epack.in/industrial-shed, https://www.epack.in/factory-building and https://www.epack.in/cold-storage-cold-room-manufacturer-supplier and 3 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 88 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
11 small tap targets
11 of 25 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “$(...).masonry is not a function”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
About 1,210 words of copy
The homepage carries about 1,210 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: “Call for support”.
9 calls to action
The homepage has 9 calls to action, for example “Get a quote”, “Contact Us” and “Call for support”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 24 testimonial or review blocks, 1 customer or partner logo and 2 trust badges.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 6 phone links and 4 email links.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
5 trackers load before any consent
5Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity (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.
10 cookies set on arrival
10Opening the homepage sets 10 cookies, 1 of them by other companies (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.
21 other companies contacted
Loading the homepage contacts 21 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 epack.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
- Analytics
- Google Tag Manager
- Hosting
- GoDaddy
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 34 issues on epack.in, including 21 speed issues. 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.