Website review, no card needed
epacflexibles.com website review
Visit site (opens in a new tab)Reviewed 3 November 202646 issues · 89 checks
This review found 46 issues worth fixing on epacflexibles.com, 16 of them high impact, across 89 checks. The most urgent: reduce unused JavaScript. 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
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 3.0 s |
| May 23, 2026 | 3.0 s |
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.4 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.0 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.6 s |
| Jul 18, 2026 | 2.7 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.8 s |
| Aug 8, 2026 | 2.9 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.6 s |
| Sep 12, 2026 | 2.6 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.8 s |
| Oct 17, 2026 | 3.0 s |
| Oct 24, 2026 | 3.1 s |
| Oct 31, 2026 | 3.1 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 174 ms |
| May 23, 2026 | 173 ms |
| May 30, 2026 | 179 ms |
| Jun 6, 2026 | 182 ms |
| Jun 13, 2026 | 183 ms |
| Jun 20, 2026 | 184 ms |
| Jun 27, 2026 | 187 ms |
| Jul 4, 2026 | 184 ms |
| Jul 11, 2026 | 183 ms |
| Jul 18, 2026 | 182 ms |
| Jul 25, 2026 | 178 ms |
| Aug 1, 2026 | 179 ms |
| Aug 8, 2026 | 184 ms |
| Aug 15, 2026 | 189 ms |
| Aug 22, 2026 | 203 ms |
| Aug 29, 2026 | 206 ms |
| Sep 5, 2026 | 214 ms |
| Sep 12, 2026 | 215 ms |
| Sep 19, 2026 | 213 ms |
| Sep 26, 2026 | 209 ms |
| Oct 3, 2026 | 208 ms |
| Oct 10, 2026 | 211 ms |
| Oct 17, 2026 | 216 ms |
| Oct 24, 2026 | 225 ms |
| Oct 31, 2026 | 222 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.9 s
1.7 s
2.6 s
3.4 s
4.3 s
5.1 s
6.0 s
6.8 s
Speed
Reduce unused JavaScript
1.1 s · 1.5 MBAbout 1.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Render-blocking requests
2.5 s36 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Mobile performance score: 33
33/100Your mobile performance score is 33. 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, 3.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Google CDN and site.com and others), adding 3.2 MB and 2.1 s of main-thread time.
Use efficient cache lifetimes
750 ms · 784 KiB19 files are served with short cache lifetimes, so returning visitors download them again (784 KiB).
Google Tag Manager adds 611 ms
611 msGoogle Tag Manager costs a phone 611 ms of main-thread work and 540 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.
Improve image delivery
531 KiB9 images could be 531 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google CDN adds 427 ms
427 msGoogle CDN costs a phone 427 ms of main-thread work and 736 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.
Reduce unused CSS
300 ms · 198 KiBAbout 198 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.
site.com adds 371 ms
371 mssite.com costs a phone 371 ms of main-thread work and 1.2 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 355 ms. During a long task the page ignores taps.
Facebook adds 295 ms
295 msFacebook costs a phone 295 ms of main-thread work and 349 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.
1,619 HTML elements
The page has 1,619 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Minify JavaScript
150 ms · 43 KiB43 KiB could be saved by minifying JavaScript.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 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.
1 checks passed
Server response: 32 ms
32 msYour server sent the HTML in 32 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.
Speed Index: 15.5 s
15.5 sVisually, the page fills in at 15.5 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 36.4 s
36.4 sThe page becomes fully interactive after 36.4 s. Good is under 3.8 s.
First Contentful Paint: 6.9 s
6.9 sThe first text or image appears after 6.9 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 6.9 s
6.9 sYour largest element takes 6.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “That means more sales. More connections with your customers…”.
Total Blocking Time: 1.1 s
1.1 sScripts block taps and scrolling for 1.1 s in total while the page loads. Good is under 200 ms.
Real-user LCP: 2.8 s
2.8 sReal visitors wait 2.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 29% slower for real visitors
+29%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 174 ms to 222 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Real-user FCP: 2.8 s
2.8 sReal visitors see the first content after 2.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.3 s
1.3 sReal visitors wait 1.3 s for your server to start answering (75th percentile). Good is under 800 ms.
23 images without width and height
23 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
+4%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.0 s to 3.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 185 ms
185 msReal visitors wait 185 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.07
0.07For real visitors the layout shifts by 0.07 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.055
0.055The layout barely moves while loading (CLS 0.055, good is under 0.1).
Images and page weight
Page weight: 14.1 MB in 197 requests
14.1 MBYour homepage downloads 14.1 MB in 197 requests on a phone: images 9.8 MB (54), scripts 3.4 MB (64) and other files 412 KiB (43). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 8.4 MB together. On a phone connection a single image that size takes seconds.
6 images far larger than shown
8.1 MB6 images are downloaded at several times the size a phone draws them, for example Post-consumer-recyle-mockup-bag.png at 4,000 px wide, shown at 291 px. Resized copies would save about 8.1 MB.
9 images in older formats
9 images (9.0 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.
7 images below the first screen load straight away
7 images further down the page (8.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 4.0 g of CO₂ per visit
4.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.00 g of CO₂e: 480.0 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
30 text elements with low contrast
30 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
9 links without text
9 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.
Headings skip levels
Headings skip levels (h2 → h4 and h2 → h4), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (10 elements).
1 checks passed
49 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 49 passed and 4 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is long (219 characters)
Your meta description is 219 characters; Google truncates after about 160, so the end of your pitch is cut.
18 links with vague text
18 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
207 internal links, 10 external
The homepage links to 207 pages on epacflexibles.com and 10 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Flexible Packaging That Does More”.
Title: 45 characters
Your title is a healthy 45 characters: “ePac Custom Flexible Packaging Company in USA”.
Canonical URL set
The canonical URL is https://epacflexibles.com/.
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://epacflexibles.com/sitemap_index.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. 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://epacflexibles.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 (2,883 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share a title
https://epacflexibles.com/shop, https://epacflexibles.com/shop/pouch-style/0/stand-up/0, https://epacflexibles.com/shop/pouch-style/0/lay-flat/0 and https://epacflexibles.com/shop/orders all use the title “Custom Pouch Packaging for Ecommerce & Retail - ePac Flexibles”. Search engines can't tell which page to show for a search, so each competes with the others.
4 pages without a meta description
https://epacflexibles.com/shop, https://epacflexibles.com/shop/pouch-style/0/stand-up/0, https://epacflexibles.com/shop/pouch-style/0/lay-flat/0 and https://epacflexibles.com/shop/orders have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages share a meta description
https://epacflexibles.com/en-ca, https://epacflexibles.com/en-gb and https://epacflexibles.com/en-gh use the same meta description. A description written for each page earns more clicks.
4 pages without an H1
https://epacflexibles.com/shop, https://epacflexibles.com/shop/pouch-style/0/stand-up/0, https://epacflexibles.com/shop/pouch-style/0/lay-flat/0 and https://epacflexibles.com/shop/orders have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://epacflexibles.com/id-id took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 81 found) and read each the way a search engine does.
4 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.
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://bat.bing.com/action/0?ti=17492632&tm=gtm002&Ver=2&mid=39cf61e9-23ca-4cbf-89af-b67ae6de300a&bo=1&sid=ea06bcc0d7cb11f1a8b145a7ee7ef223&vid=ea06cfa0d7cb11f1bf8e35f0e89d1dea&vids=1&msclkid=N&pi=91.
3 small tap targets
3 of 9 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
6 JavaScript errors while loading
6 errors were logged to the browser console while the page loaded, for example “Property 'nodeType' is not implemented on agentforce_messaging”.
10 low-resolution images
10 images are served at too low a resolution for sharp phone screens.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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,147 words of copy
The homepage carries about 1,147 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: “GET A QUOTE” and “GET PRICING”.
26 calls to action
The homepage has 26 calls to action, for example “Shop”, “Shop by Industry” and “Contact Us”.
Social proof on the page
Social proof on the homepage: 20 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Tag Manager and Meta Pixel.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, LinkedIn Insight and Meta Pixel and 2 mores (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.
23 cookies set on arrival
23Opening the homepage sets 23 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.
38 other companies contacted
Loading the homepage contacts 38 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 epacflexibles.com, 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
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 46 issues on epacflexibles.com, including 25 speed issues and 2 SEO 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.