Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

Page Load Speed

745 ms in total

First Response

55 ms

Resources Loaded

471 ms

Page Rendered

219 ms

pepco.com screenshot

About Website

Visit pepco.com now to see the best up-to-date Pepco content for United States and also check out these interesting facts you probably never knew about pepco.com

Pepco delivers safe, reliable and affordable electric service to more than 801,000 customers in Maryland and the District of Columbia.

Visit pepco.com

Key Findings

We analyzed Pepco.com page load time and found that the first response time was 55 ms and then it took 690 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

pepco.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.4 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.1 s

0/100

25%

SI (Speed Index)

Value13.5 s

2/100

10%

TBT (Total Blocking Time)

Value1,730 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.164

72/100

15%

TTI (Time to Interactive)

Value25.3 s

0/100

10%

Network Requests Diagram

pepco.com

55 ms

www.pepco.com

71 ms

ektron.javascript.ashx

45 ms

ektron.stylesheet.ashx

32 ms

supersized.css

22 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 93% of them (54 requests) were addressed to the original Pepco.com, 3% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (129 ms) relates to the external source Googletagmanager.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 333.8 kB (30%)

Content Size

1.1 MB

After Optimization

779.3 kB

In fact, the total size of Pepco.com main page is 1.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 737.4 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 47.7 kB

  • Original 60.8 kB
  • After minification 56.7 kB
  • After compression 13.1 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 47.7 kB or 78% of the original size.

Image Optimization

-8%

Potential reduce by 55.5 kB

  • Original 737.4 kB
  • After minification 681.9 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Pepco images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 224.0 kB

  • Original 305.8 kB
  • After minification 295.8 kB
  • After compression 81.8 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 224.0 kB or 73% of the original size.

CSS Optimization

-72%

Potential reduce by 6.6 kB

  • Original 9.1 kB
  • After minification 7.3 kB
  • After compression 2.5 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Pepco.com needs all CSS files to be minified and compressed as it can save up to 6.6 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (17%)

Requests Now

53

After Optimization

44

The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pepco. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.

Accessibility Review

pepco.com accessibility score

64

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[role]s are not contained by their required parent element

High

[role] values are not valid

High

ARIA IDs are not unique

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

pepco.com best practices score

50

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

pepco.com SEO score

69

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pepco.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Pepco.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

Open Graph data is detected on the main page of Pepco. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: