3.4 sec in total
22 ms
2.7 sec
682 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 22 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
mystream.com performance score
name
value
score
weighting
Value9.4 s
0/100
10%
Value21.3 s
0/100
25%
Value10.6 s
8/100
10%
Value710 ms
42/100
30%
Value0.358
31/100
15%
Value16.7 s
5/100
10%
22 ms
187 ms
83 ms
38 ms
111 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 42% of them (40 requests) were addressed to the original Mystream.com, 18% (17 requests) were made to Maps.googleapis.com and 14% (13 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (839 ms) relates to the external source Use.typekit.net.
Page size can be reduced by 794.3 kB (13%)
6.2 MB
5.4 MB
In fact, the total size of Mystream.com main page is 6.2 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. 65% of websites need less resources to load. Images take 5.1 MB which makes up the majority of the site volume.
Potential reduce by 117.8 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. This page needs HTML code to be minified as it can gain 26.2 kB, which is 18% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 117.8 kB or 83% of the original size.
Potential reduce by 112.0 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. My Stream images are well optimized though.
Potential reduce by 558.0 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 558.0 kB or 65% of the original size.
Potential reduce by 6.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. Mystream.com needs all CSS files to be minified and compressed as it can save up to 6.5 kB or 74% of the original size.
Number of requests can be reduced by 41 (51%)
81
40
The browser has sent 81 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 25 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
mystream.com
22 ms
mystream.com
187 ms
di.js
83 ms
bundle
38 ms
legacybundle
111 ms
api.js
82 ms
obg4jvp.js
246 ms
js
211 ms
foresee-trigger.js
78 ms
pattern_bg.png
9 ms
recaptcha__en.js
125 ms
printbundle
34 ms
4a5
77 ms
gtm.js
400 ms
header_background_gloabl.png
57 ms
bundle-save.ashx
61 ms
logo-desktop.png
342 ms
icon-sd464708c8e.png
343 ms
home_header_energy_icon.png
340 ms
home_header_mobile_icon.png
342 ms
home_header_protect_icon.png
395 ms
module_background.png
395 ms
light.jpg
395 ms
flame.jpg
394 ms
ShopPhones.jpg
393 ms
BringPhones.jpg
396 ms
check.png
396 ms
single_phone_white.png
397 ms
multi_phone_dark.png
396 ms
close.png
394 ms
ly7opQzC_VsUg8Lh8bWevXwSfgDENzsks5cfu3aNpnXffFVqggMWeMI6MK6f5Mb.eot
370 ms
hjJr9GbpAQfb6a2-TAB6HyknDUilmLzRXwtT0TaJwEJffHAsgsMWeMI6MK6f5Mt.eot
490 ms
S2nTKODEqDNq6mvsiKoXRpspUNhV6SixB5jE9HkSulIffHcsgsMWeMI6MK6f5gI.eot
571 ms
l-MSMxIEfwLLJ7fy_UP0EyIn-KBHEtgTnrGFEphO2obffHPsgsMWeMI6MK6f5Mb.eot
554 ms
QkzV5dk_fdS_CQOrBGXMFDjyJvG0TNSSVrTqMPmy2UMff4kQgsMWeMI6MK6f5MS.eot
571 ms
hTow86eOnSnY-EcIf4JsAwQYBjTU-weuBAnXjS9N0d9ffHesgsMWeMI6MK6f5MC.eot
569 ms
ULLEX4rlE1X5RewyBhV9PBi2e8Khy3TztgNYZJ2Jw39ffH5sgsMWeMI6MK6f5MX.eot
570 ms
r5IxikLZiTVPMhRi3B6wYfq22trlNWz7eQhUQl3LGFwffHpsgsMWeMI6MK6f5gM.eot
570 ms
dan2ByVLF-eOcxoUdtxPSGyxfx3xaSgNrefpPwaczwbffHfsgsMWeMI6MK6f5MI.eot
607 ms
o79MxI_FywUk4uWBbVfq4eixn935vYb-7m4JXAaCA4XffHHsgsMWeMI6MK6f5Mw.eot
839 ms
3_ao6QnM67fFKxfrdUgz5JHDTsPLIwASiczdCO-ucAJffH-sgsMWeMI6MK6f5Mj.eot
836 ms
mask_icon.png
329 ms
monitor_icon.png
368 ms
cloud_protection_icon.png
332 ms
none
371 ms
footer-section-bottom-rule.png
368 ms
logo-footer.png
368 ms
bbb2x.png
368 ms
dsa.png
370 ms
common.js
168 ms
map.js
212 ms
loading.gif
140 ms
check.png
140 ms
Home_carrousel_electricity_image_0615.ashx
692 ms
Home_carrousel_002_0615.ashx
689 ms
Home_carrousel_003_0615.ashx
710 ms
Home_carousel_lyric_image.ashx
681 ms
foresee-surveydef.js
186 ms
analytics.js
269 ms
quant.js
260 ms
j.php
225 ms
1765999.js
644 ms
page-not-found.aspx
115 ms
util.js
79 ms
onion.js
79 ms
openhand_8_8.cur
490 ms
stats.js
115 ms
controls.js
128 ms
ViewportInfoService.GetViewportInfo
355 ms
foresee-dhtml.css
71 ms
v.gif
43 ms
pixel;r=744552496;a=p-T9mJH_gLAC_3p;fpan=1;fpa=P0-1422860278-1456782633788;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456782633786;tzo=-180;ref=;url=https%3A%2F%2Fmystream.com%2F;ogl=
370 ms
linkid.js
302 ms
css
285 ms
transparent.png
222 ms
google4.png
195 ms
mapcnt6.png
221 ms
sv5.png
221 ms
tmapctrl.png
230 ms
tmapctrl4.png
229 ms
places_impl.js
134 ms
vt
35 ms
vt
67 ms
vt
65 ms
vt
47 ms
vt
48 ms
vt
68 ms
vt
67 ms
collect
21 ms
collect
86 ms
powered-by-google-on-white3.png
44 ms
autocomplete-icons.png
45 ms
AuthenticationService.Authenticate
14 ms
nr-852.min.js
60 ms
__ptq.gif
43 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
Registers an unload listener
Detected JavaScript libraries
Uses deprecated APIs
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
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: