Website review, no card needed
edenorte.com.do website review
Visit site (opens in a new tab)Reviewed 19 November 202639 issues · 66 checks
This review found 39 issues worth fixing on edenorte.com.do, 11 of them high impact, across 66 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
71CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.7 s |
| May 23, 2026 | 2.7 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.6 s |
| Jun 13, 2026 | 2.6 s |
| Jun 20, 2026 | 2.7 s |
| Jun 27, 2026 | 2.7 s |
| Jul 4, 2026 | 2.7 s |
| Jul 11, 2026 | 2.7 s |
| Jul 18, 2026 | 2.6 s |
| Jul 25, 2026 | 2.5 s |
| Aug 1, 2026 | 2.5 s |
| Aug 8, 2026 | 2.4 s |
| Aug 15, 2026 | 2.4 s |
| Aug 22, 2026 | 2.4 s |
| Aug 29, 2026 | 2.4 s |
| Sep 5, 2026 | 2.5 s |
| Sep 12, 2026 | 2.5 s |
| Sep 19, 2026 | 2.6 s |
| Sep 26, 2026 | 2.6 s |
| Oct 3, 2026 | 2.5 s |
| Oct 10, 2026 | 2.6 s |
| Oct 17, 2026 | 2.6 s |
| Oct 24, 2026 | 2.5 s |
| Oct 31, 2026 | 2.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 170 ms |
| May 23, 2026 | 171 ms |
| May 30, 2026 | 171 ms |
| Jun 6, 2026 | 171 ms |
| Jun 13, 2026 | 171 ms |
| Jun 20, 2026 | 170 ms |
| Jun 27, 2026 | 171 ms |
| Jul 4, 2026 | 174 ms |
| Jul 11, 2026 | 171 ms |
| Jul 18, 2026 | 171 ms |
| Jul 25, 2026 | 172 ms |
| Aug 1, 2026 | 170 ms |
| Aug 8, 2026 | 172 ms |
| Aug 15, 2026 | 174 ms |
| Aug 22, 2026 | 173 ms |
| Aug 29, 2026 | 177 ms |
| Sep 5, 2026 | 178 ms |
| Sep 12, 2026 | 181 ms |
| Sep 19, 2026 | 184 ms |
| Sep 26, 2026 | 188 ms |
| Oct 3, 2026 | 192 ms |
| Oct 10, 2026 | 195 ms |
| Oct 17, 2026 | 201 ms |
| Oct 24, 2026 | 198 ms |
| Oct 31, 2026 | 194 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.6 s
1.2 s
1.8 s
2.4 s
3.0 s
3.6 s
4.1 s
4.7 s
Speed
Use efficient cache lifetimes
2.0 s · 7.1 MB100 files are served with short cache lifetimes, so returning visitors download them again (7.1 MB).
Render-blocking requests
2.5 s37 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.5 s.
Improve image delivery
150 ms · 2.9 MB5 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 150 ms faster on a phone.
Reduce unused JavaScript
1.7 MBAbout 1.7 MB of JavaScript is downloaded but never used on this page.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Tag Manager and Facebook and others), adding 2.8 MB and 1.1 s of main-thread time.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Reduce unused CSS
750 ms · 239 KiBAbout 239 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 750 ms faster on a phone.
YouTube adds 356 ms
356 msYouTube costs a phone 356 ms of main-thread work and 1,002 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.
Google Tag Manager adds 336 ms
336 msGoogle Tag Manager costs a phone 336 ms of main-thread work and 669 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.5 s
A phone's processor spends 3.5 s on main-thread work while loading, 1.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,894 HTML elements
The page has 1,894 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google Maps adds 127 ms
127 msGoogle Maps costs a phone 127 ms of main-thread work and 409 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.
Vimeo adds 65 ms
65 msVimeo costs a phone 65 ms of main-thread work and 363 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.
12 long tasks on the main thread
12 long tasks block the main thread while loading, the longest for 159 ms. During a long task the page ignores taps.
Font display
150 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).
Legacy JavaScript
27 KiBPolyfills for old browsers add 27 KiB JavaScript that modern phones do not need.
Minify JavaScript
17 KiB17 KiB could be saved by minifying JavaScript.
Minify CSS
9 KiB9 KiB could be saved by minifying CSS.
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: 40 ms
40 msYour server sent the HTML in 40 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.
Time to Interactive: 38.0 s
38.0 sThe page becomes fully interactive after 38.0 s. Good is under 3.8 s.
Speed Index: 9.1 s
9.1 sVisually, the page fills in at 9.1 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 5.6 s
5.6 sYour largest element takes 5.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Edenorte Dominicana”.
First Contentful Paint: 3.3 s
3.3 sThe first text or image appears after 3.3 s on a phone. Good is under 1.8 s.
Real-user INP: 202 ms
202 msReal visitors wait 202 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 2.3 s
2.3 sReal visitors see the first content after 2.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 1.2 s
1.2 sReal visitors wait 1.2 s for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 444 ms
444 msScripts block taps and scrolling for 444 ms in total while the page loads. Good is under 200 ms.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
3 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.045
0.045The layout barely moves while loading (CLS 0.045, good is under 0.1).
Images and page weight
Page weight: 10.7 MB in 177 requests
10.7 MBYour homepage downloads 10.7 MB in 177 requests on a phone: images 5.9 MB (26), scripts 3.3 MB (63) and fonts 613 KiB (13). Under 2 MB keeps phones on slow connections fast.
About 3.0 g of CO₂ per visit
3.02 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.02 g of CO₂e: 362.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
4 images without alt text
4 images have no alt text, which hurts accessibility and image search.
9 text elements with low contrast
9 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
7 links without text
7 links have no text or label, so screen readers cannot say where they go.
Frames without titles
2 frames have no title, so screen-reader users cannot tell what they contain.
Positive tabindex
1 element has a tabindex above 0, which scrambles the keyboard order.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (24 characters)
Your title is only 24 characters: “EDENORTE DOMINICANA S.A.”. Between 30 and 65 characters leaves room to say what you do and for whom.
No XML sitemap
No XML sitemap at https://edenorte.com.do/sitemap.xml, so Google discovers your pages only by following links.
No robots.txt
There is no robots.txt at edenorte.com.do/robots.txt, the first file search crawlers ask for.
1 link crawlers can't follow
1 link has no real href, so search engines can't follow it.
80 internal links, 142 external
The homepage links to 80 pages on edenorte.com.do and 142 external pages.
4 checks passed
Meta description: 155 characters
Your meta description is 155 characters: “La Empresa Distribuidora de Electricidad del Norte S.A. (EDENORTE Dominicana S.A.), tiene la concesión de la comerciali…”.
Canonical URL set
The canonical URL is https://edenorte.com.do/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
AI search readiness
1 checks passed
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.
Other pages
Your server turned our page checks away
15 pages we tried to fetch timed out or refused automated requests, so these checks couldn't run. Some firewalls do this to every bot, including search engine crawlers they don't recognise.
Best practices
7 third-party cookies
7 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).
4 distorted images
4 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
2 console errors
2 errors were logged to the browser console during Google's test (“Failed to load resource: the server responded with a status of 429 (Too Many Requests)”).
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
Phone number is not tap-to-call
Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.
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,160 words of copy
The homepage carries about 1,160 words of visible text.
3 checks passed
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 6 testimonial or review blocks and 1 trust badge.
Analytics in place
Analytics detected: Google Analytics and Meta Pixel.
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 edenorte.com.do, 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 Analytics
- Hosting
- Azure
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 39 issues on edenorte.com.do, including 23 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.