Website review, no card needed
epconcommunities.com website review
Visit site (opens in a new tab)Reviewed 25 October 202650 issues · 89 checks
This review found 50 issues worth fixing on epconcommunities.com, 17 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
66DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 3.6 s |
| May 9, 2026 | 3.6 s |
| May 16, 2026 | 3.7 s |
| May 23, 2026 | 3.7 s |
| May 30, 2026 | 3.7 s |
| Jun 6, 2026 | 3.6 s |
| Jun 13, 2026 | 3.6 s |
| Jun 20, 2026 | 3.6 s |
| Jun 27, 2026 | 3.6 s |
| Jul 4, 2026 | 3.5 s |
| Jul 11, 2026 | 3.5 s |
| Jul 18, 2026 | 3.6 s |
| Jul 25, 2026 | 3.7 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.6 s |
| Aug 22, 2026 | 3.6 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.4 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.4 s |
| Oct 3, 2026 | 3.5 s |
| Oct 10, 2026 | 3.5 s |
| Oct 17, 2026 | 3.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 171 ms |
| May 9, 2026 | 171 ms |
| May 16, 2026 | 163 ms |
| May 23, 2026 | 165 ms |
| May 30, 2026 | 164 ms |
| Jun 6, 2026 | 171 ms |
| Jun 13, 2026 | 170 ms |
| Jun 20, 2026 | 171 ms |
| Jun 27, 2026 | 172 ms |
| Jul 4, 2026 | 175 ms |
| Jul 11, 2026 | 172 ms |
| Jul 18, 2026 | 170 ms |
| Jul 25, 2026 | 161 ms |
| Aug 1, 2026 | 158 ms |
| Aug 8, 2026 | 167 ms |
| Aug 15, 2026 | 170 ms |
| Aug 22, 2026 | 173 ms |
| Aug 29, 2026 | 179 ms |
| Sep 5, 2026 | 179 ms |
| Sep 12, 2026 | 180 ms |
| Sep 19, 2026 | 183 ms |
| Sep 26, 2026 | 179 ms |
| Oct 3, 2026 | 179 ms |
| Oct 10, 2026 | 182 ms |
| Oct 17, 2026 | 187 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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
4.3 s · 1,018 KiBAbout 1,018 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.3 s faster on a phone.
Use efficient cache lifetimes
950 ms · 12.4 MB59 files are served with short cache lifetimes, so returning visitors download them again (12.4 MB).
Improve image delivery
11.1 MB33 images could be 11.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Mobile performance score: 57
57/100Your mobile performance score is 57 (desktop: 53). Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Accessibe Accessibility Overlay and others), adding 1.5 MB and 806 ms of main-thread time.
Render-blocking requests
750 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.
Google Tag Manager adds 409 ms
409 msGoogle Tag Manager costs a phone 409 ms of main-thread work and 700 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: 2.7 s
A phone's processor spends 2.7 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Facebook adds 175 ms
175 msFacebook costs a phone 175 ms of main-thread work and 305 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.
15 long tasks on the main thread
15 long tasks block the main thread while loading, the longest for 150 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).
Reduce unused CSS
13 KiBAbout 13 KiB of CSS is downloaded but never applied on this page.
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.
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.
Real-user CLS: 0.54
0.54For real visitors the layout shifts by 0.54 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 14.8 s
14.8 sYour largest element takes 14.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “This site uses cookies to improve your experience and to he…”.
Time to Interactive: 18.9 s
18.9 sThe page becomes fully interactive after 18.9 s. Good is under 3.8 s.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 3.0 s
3.0 sReal visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Total Blocking Time: 446 ms
446 msScripts block taps and scrolling for 446 ms in total while the page loads. Good is under 200 ms.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+8%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 171 ms to 187 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 3.6 s to 3.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user INP: 145 ms
145 msReal visitors wait 145 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.2 s
1.2 sReal visitors see the first content after 1.2 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 634 ms
634 msReal visitors wait 634 ms for your server to start answering (75th percentile). Good is under 800 ms.
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.
Cumulative Layout Shift: 0.003
0.003The layout barely moves while loading (CLS 0.003, good is under 0.1).
Images and page weight
Page weight: 18.1 MB in 163 requests
18.1 MBYour homepage downloads 18.1 MB in 163 requests on a phone: images 11.9 MB (55), other files 3.8 MB (58) and scripts 2.2 MB (42). Under 2 MB keeps phones on slow connections fast.
33 images far larger than shown
9.6 MB33 images are downloaded at several times the size a phone draws them, for example 1791644592681.jpg at 4,781 px wide, shown at 360 px. Resized copies would save about 9.6 MB.
3 images over 500 KB
3 images weigh 6.0 MB together. On a phone connection a single image that size takes seconds.
32 images below the first screen load straight away
32 images further down the page (11.5 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 5.1 g of CO₂ per visit
5.12 gBy the Sustainable Web Design model, a visit to your homepage emits about 5.12 g of CO₂e: 614.0 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
ARIA attributes must conform to valid values (3 elements)
ARIA attributes must conform to valid values: 3 elements on the page fail this check, rated critical by axe-core.
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
5 text elements with low contrast
5 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
8 images without alt text
8 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (19 elements)
All page content should be contained by landmarks: 19 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails 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.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 10 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.
Title is long (75 characters)
Your title is 75 characters, so Google will cut it off around 60: “New Home Builders, Home Development & Home Construction | Epcon Communities”.
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 (313 characters)
Your meta description is 313 characters; Google truncates after about 160, so the end of your pitch is cut.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.epconcommunities.com/sitemap.xml, so Google discovers your pages only by following links.
9 links crawlers can't follow
9 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.
20 internal links, 0 external
The homepage links to 20 pages on epconcommunities.com and 0 external pages.
2 checks passed
Structured data in place
Structured data found: WebSite.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
AI search readiness
Most text only appears after JavaScript runs
29%A phone browser shows 397 words, but the HTML your server sends has only 116. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.
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://www.epconcommunities.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.
1 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.
Other pages
11 pages share 3 titles
/, https://www.epconcommunities.com/testimonials, https://www.epconcommunities.com/about/why-epcon, https://www.epconcommunities.com/about/faqs, https://www.epconcommunities.com/about/our-history and https://www.epconcommunities.com/contact and 1 other all use the title “New Home Builders, Home Development & Home Construction | Epcon Commu…”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
2 pages without a meta description
https://www.epconcommunities.com/find-your-home/communities and https://www.epconcommunities.com/find-your-home/quick-move-in-homes have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages share a meta description
https://www.epconcommunities.com/testimonials, https://www.epconcommunities.com/about/why-epcon, https://www.epconcommunities.com/about/faqs, https://www.epconcommunities.com/about/our-history, https://www.epconcommunities.com/contact and https://www.epconcommunities.com/contact/for-agents use the same meta description. A description written for each page earns more clicks.
10 pages without an H1
https://www.epconcommunities.com/testimonials, https://www.epconcommunities.com/epcon-insights, https://www.epconcommunities.com/find-your-home/communities, https://www.epconcommunities.com/find-your-home/quick-move-in-homes, https://www.epconcommunities.com/about/why-epcon and https://www.epconcommunities.com/about/faqs and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
10 pages with very little text
https://www.epconcommunities.com/testimonials, https://www.epconcommunities.com/epcon-insights, https://www.epconcommunities.com/find-your-home/communities, https://www.epconcommunities.com/find-your-home/quick-move-in-homes, https://www.epconcommunities.com/about/why-epcon and https://www.epconcommunities.com/about/our-history and 4 others have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 16 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
2 small tap targets
2 of 7 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
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.
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
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 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 397 words of copy
The homepage carries about 397 words of visible text.
2 checks passed
3 calls to action
The homepage has 3 calls to action, for example “Contact” and “Contact Us”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Hotjar and Meta Pixel and 1 more (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.
18 cookies set on arrival
18Opening the homepage sets 18 cookies (measured from a US location before any click).
30 other companies contacted
Loading the homepage contacts 30 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: CookieYes
A consent management tool (CookieYes) loads with the page.
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 epconcommunities.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Angular
- 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 50 issues on epconcommunities.com, including 17 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.