Southern California Edison - SCE

Mobile Usability



Mobile Speed



Last tested: 2017-08-29

Rescan Mobile Speed: 55/100 Mobile Speed Test Quick Overview

Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 7 blocking script resources and 4 blocking CSS resources. This causes a delay in rendering your page.!ut/p/diges…rtal_80__0.0%3Ahead_js…9e55f7a51cd686b11f7.js…ferrer=&mboxVersion=40…ferrer=&mboxVersion=40…ferrer=&mboxVersion=40!ut/p/diges…3Aconfig_config_static!ut/p/diges…s_bar__0.0%3Aconfig_js
Optimize CSS Delivery of the following:!ut/p/diges…et_css__0.0%3Ahead_css!ut/p/diges…et_css__0.0%3Ahead_css!ut/p/diges…et_css__0.0%3Ahead_css!ut/p/diges…et_css__0.0%3Ahead_css
Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.
Leverage browser caching for the following cacheable resources:…9e55f7a51cd686b11f7.js (expiration not specified)…17364746d6b6b0042aa.js (expiration not specified)…mory,CACHE_RELOAD,LOGN (5 minutes) (20 minutes) (30 minutes) (30 minutes) (60 minutes) (2.2 hours) (2.2 hours) (2.2 hours) (2.2 hours) (2.2 hours) (2.2 hours) (2.2 hours)!ut/p/diges…3Aconfig_config_static (24 hours)
Avoid landing page redirects

Your page has 2 redirects. Redirects introduce additional delays before the page can be loaded.
Avoid landing page redirects for the following chain of redirected URLs.!ut/p/b1/04_Sj…/L2dBISEvZ0FBIS9nQSEh/
Prioritize visible content

Your page requires additional network round trips to render the above-the-fold content. For best performance, reduce the amount of HTML needed to render above-the-fold content.
The entire HTML response was not sufficient to render the above-the-fold content. This usually indicates that additional resources, loaded after HTML parsing, were required to render above-the-fold content. Prioritize visible content that is needed for rendering above-the-fold by including it directly in the HTML response.
Only about 35% of the final above-the-fold content could be rendered with the full HTML response.
Reduce server response time

Optimize images

Properly formatting and compressing images can save many bytes of data.
Optimize the following images to reduce their size by 5.5KiB (30% reduction).
Compressing…/widgetIconsSprite.png could save 4.1KiB (30% reduction).
Compressing…onsive/images/logo.png could save 1.4KiB (30% reduction).
Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.
Minify HTML for the following resources to reduce their size by 5.4KiB (31% reduction).
Minifying!ut/p/b1/04_Sj…/L2dBISEvZ0FBIS9nQSEh/ could save 5.4KiB (31% reduction) after compression.
Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.
Minify CSS for the following resources to reduce their size by 4.4KiB (13% reduction).
Minifying!ut/p/diges…et_css__0.0%3Ahead_css could save 4.4KiB (13% reduction) after compression.
Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.
Minify JavaScript for the following resources to reduce their size by 930B (76% reduction).
Minifying could save 930B (76% reduction) after compression. Mobile Resources

Total Resources49
Number of Hosts18
Static Resources30
JavaScript Resources27
CSS Resources4 Mobile Resource Breakdown