5 sec in total
384 ms
4.3 sec
345 ms
Click here to check amazing My Stream content for United States. Otherwise, check out these important facts you probably never knew about mystream.com
Looking for an energy plan that fits your lifestyle? Stream energy plans have simple pricing with dependable service and a Customer Support team ready to help!
Visit mystream.comWe analyzed Mystream.com page load time and found that the first response time was 384 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
mystream.com performance score
name
value
score
weighting
Value8.4 s
0/100
10%
Value15.0 s
0/100
25%
Value11.4 s
5/100
10%
Value2,610 ms
4/100
30%
Value0.501
16/100
15%
Value19.9 s
2/100
10%
384 ms
470 ms
380 ms
141 ms
114 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 40% of them (45 requests) were addressed to the original Mystream.com, 19% (21 requests) were made to Assets.adobedtm.com and 11% (12 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Mystream.com.
Page size can be reduced by 270.0 kB (53%)
513.3 kB
243.3 kB
In fact, the total size of Mystream.com main page is 513.3 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. 70% of websites need less resources to load. Javascripts take 263.1 kB which makes up the majority of the site volume.
Potential reduce by 190.2 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 190.2 kB or 79% of the original size.
Potential reduce by 79.1 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 79.1 kB or 30% of the original size.
Potential reduce by 773 B
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. Mystream.com has all CSS files already compressed.
Number of requests can be reduced by 72 (76%)
95
23
The browser has sent 95 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Stream. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 61 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
mystream.com
384 ms
470 ms
ruxitagentjs_ANVfqrux_10289240325103055.js
380 ms
launch-f5821d276298.min.js
141 ms
gtm.js
114 ms
fbevents.js
62 ms
public.css
1090 ms
obg4jvp.js
139 ms
validationEngine.jquery.css
541 ms
jquery-3.5.1.js
913 ms
jquery-ui-1.12.1.js
1163 ms
jquery.ui.form.js
573 ms
jquery.tablesorter.min.js
105 ms
jquery.stream.validationEngine.js
769 ms
jquery.stream.validationEngine-rules.js
735 ms
jspdf.min.js
136 ms
slick.min.js
768 ms
jquery-ui.css
105 ms
common.css
921 ms
common-oe.css
938 ms
layout.css
948 ms
slick.css
1159 ms
localStorage.js
1211 ms
common.js
1211 ms
common-oe.js
1211 ms
js.cookie-2.2.1.min.js
1275 ms
lodash.min.js
1289 ms
luxon.js
1303 ms
ajax.js
1310 ms
streamglobal.js
1311 ms
customer_enrollment.js
1492 ms
layout.js
1466 ms
user_cart.js
1481 ms
moment.js
1495 ms
StreamOneTag.js
1491 ms
StreamEgainChat.js
1481 ms
oe_residential_confirmation.js
1663 ms
id
37 ms
AppMeasurement.min.js
17 ms
AppMeasurement_Module_ActivityMap.min.js
16 ms
egain-chat.js
604 ms
Offers.egain
606 ms
EG91271108
451 ms
loading.gif
242 ms
electric_tcm367-26435.png
244 ms
gas_tcm367-27615.png
245 ms
renewable_tcm367-27629.png
243 ms
home-energy_tcm367-27589.png
642 ms
business-energy_tcm367-27545.png
923 ms
dest5.html
24 ms
pixel
29 ms
pixel
16 ms
ibs:dpid=771&dpuuid=CAESEBqyCra3F7UjEb0QDh-nW-g&google_cver=1
6 ms
quant.js
20 ms
generic
16 ms
generic
3 ms
ibs:dpid=903&dpuuid=0d2c1233-cb68-4638-8d2f-80cafcf148d4
5 ms
sdk.js
15 ms
alert-exclamation.png
311 ms
header-logo.svg
312 ms
icon-sd62c859559.png
632 ms
alert.png
310 ms
module_background.png
508 ms
green-bg_tcm367-27539.jpg
500 ms
logo-footer.png
509 ms
sdk.js
163 ms
d
203 ms
d
238 ms
d
257 ms
d
278 ms
d
279 ms
RC41684a6bb6c747fab3aabd4302fd4a60-source.min.js
225 ms
RC6358397b58c447598df7e68d508a4e58-source.min.js
223 ms
RC89f9450bbad04e39b685487737ef479d-source.min.js
244 ms
analytics.js
161 ms
80584140.js
154 ms
d
127 ms
d
130 ms
d
150 ms
d
150 ms
d
151 ms
d
200 ms
chat-now-icon.svg
360 ms
linkid.js
36 ms
hotjar-1542831.js
199 ms
egain-docked-chat.js
64 ms
collect
30 ms
collect
48 ms
collect
32 ms
p.gif
34 ms
RCbe3ecd74920d4a4c8819e5a87e4452c2-source.min.js
29 ms
controller.php
39 ms
js
43 ms
collect
23 ms
js
133 ms
RCaedd5e50f20a4795ab2788d73fcbfff9-source.min.js
10 ms
RC7de81141aa994dbb8ce51a121be56157-source.min.js
5 ms
RCf02f6bee0f324c03a011e357d7552fce-source.min.js
74 ms
modules.404c8789d11e259a4872.js
75 ms
print.css
198 ms
RCc0afdbc6739f45f79f41a9bdb8576fd8-source.min.js
8 ms
RC77bc1741162945fa8ad5fd5ff784bc70-source.min.js
7 ms
RCb0251d8b261744eaa2f58ebac2408949-source.min.js
46 ms
RC482d7f93d1b64df3b5b09c5a9370c59b-source.min.js
46 ms
RCac7b74b312194c2098f36c368bf18901-source.min.js
5 ms
RC84d4d8caf70c4707bbd0f580be47b594-source.min.js
6 ms
RC1f44c0a14b10455a8c492fed512e143f-source.min.js
6 ms
RCcb680e5d18684a21b2e0c62612b76215-source.min.js
6 ms
s14384445729665
27 ms
RC341894d8068c4f598becc4bc5095136a-source.min.js
14 ms
RCf29d30d9744243d3acb4bc0bf398e9e8-source.min.js
4 ms
RC1d7732d7f0dd4d828478b3b938375e64-source.min.js
4 ms
collect
21 ms
mystream.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Links do not have a discernible name
mystream.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
mystream.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
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
Tap targets are not sized appropriately
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mystream.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 Mystream.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.
mystream.com
Open Graph description is not detected on the main page of My Stream. 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: