2.3 sec in total
38 ms
2.1 sec
200 ms
Visit support.comed.com now to see the best up-to-date Support Com Ed content for United States and also check out these interesting facts you probably never knew about support.comed.com
Powering lives in northern Illinois. Pay your bill, report an outage, start or stop your service, and explore energy saving programs.
Visit support.comed.comWe analyzed Support.comed.com page load time and found that the first response time was 38 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
support.comed.com performance score
name
value
score
weighting
Value10.1 s
0/100
10%
Value21.4 s
0/100
25%
Value12.2 s
3/100
10%
Value2,760 ms
3/100
30%
Value0.487
17/100
15%
Value27.0 s
0/100
10%
38 ms
128 ms
1037 ms
80 ms
80 ms
Our browser made a total of 44 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original Support.comed.com, 52% (23 requests) were made to S3.amazonaws.com and 23% (10 requests) were made to Comed.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source S3.amazonaws.com.
Page size can be reduced by 490.2 kB (68%)
717.2 kB
227.0 kB
In fact, the total size of Support.comed.com main page is 717.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Javascripts take 462.2 kB which makes up the majority of the site volume.
Potential reduce by 48.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 48.1 kB or 78% of the original size.
Potential reduce by 8.7 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. Obviously, Support Com Ed needs image optimization as it can save up to 8.7 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 309.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 309.8 kB or 67% of the original size.
Potential reduce by 123.7 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. Support.comed.com needs all CSS files to be minified and compressed as it can save up to 123.7 kB or 84% of the original size.
Number of requests can be reduced by 22 (54%)
41
19
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Support Com Ed. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
support.comed.com
38 ms
support.comed.com
128 ms
lib.js
1037 ms
smartsupport.js
80 ms
theme.css
80 ms
theme.js
59 ms
jquery.colorbox-min.js
177 ms
jquery.cookie.js
186 ms
ga.js
122 ms
body_bg_ltbluegradient.png
147 ms
enewshome.aspx
69 ms
header-bg-gray.png
744 ms
logo-ComEd.png
58 ms
enews_tab_250.png
68 ms
pipe_777.jpg
66 ms
icon_facebook.png
68 ms
icon_youtube.png
140 ms
icon_print.png
79 ms
icon_textsize.png
80 ms
twitter-bird-white-on-blue.png
64 ms
icon_flickr.png
105 ms
btn_searcharrow.png
104 ms
loginbox_tab.png
58 ms
loginbox_content_trans_bg.png
66 ms
navigation_public.png
66 ms
navigation_tabs.png
84 ms
nav_shadow.png
85 ms
bullet_arrow_red_down.png
91 ms
bullet_arrow_red.png
117 ms
bullet.gif
117 ms
gtm.js
119 ms
sprite.png
82 ms
screen.css
90 ms
EnewsSignUp.js
77 ms
__utm.gif
32 ms
__utm.gif
26 ms
analytics.js
55 ms
gradient-toolform.png
34 ms
btn_searcharrow_white.png
33 ms
linkid.js
12 ms
collect
11 ms
collect
54 ms
print.css
8 ms
nr-885.min.js
52 ms
support.comed.com accessibility score
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
[aria-*] attributes do not match their roles
[role]s are not contained by their required parent element
[role] values are not valid
ARIA IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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
Image elements do not have [alt] attributes
support.comed.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
support.comed.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Support.comed.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 Support.comed.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.
support.comed.com
Open Graph description is not detected on the main page of Support Com Ed. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: