Tools & Wizards About Us
myaccount2.orlandosentinel.com screenshot

Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

myaccount2.orlandosentinel.com

Orlando Sentinel - Under Construction

Page Load Speed

916 ms in total

First Response

42 ms

Resources Loaded

662 ms

Page Rendered

212 ms

myaccount2.orlandosentinel.com screenshot

About Website

Visit myaccount2.orlandosentinel.com now to see the best up-to-date Myaccount 2 Orlando Sentinel content for United States and also check out these interesting facts you probably never knew about myaccount2.orlandosentinel.com

Orlando Sentinel - Under Construction

Visit myaccount2.orlandosentinel.com

Key Findings

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

Performance Metrics

myaccount2.orlandosentinel.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value13.1 s

0/100

25%

SI (Speed Index)

Value13.1 s

2/100

10%

TBT (Total Blocking Time)

Value2,590 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.152

75/100

15%

TTI (Time to Interactive)

Value12.9 s

13/100

10%

Network Requests Diagram

myaccount2.orlandosentinel.com

42 ms

myaccount2.orlandosentinel.com

99 ms

main.css

60 ms

jquery-ui-1.10.3.custom.min.css

71 ms

jquery.min.js

80 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 79% of them (44 requests) were addressed to the original Myaccount2.orlandosentinel.com, 16% (9 requests) were made to S3.amazonaws.com and 2% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (247 ms) relates to the external source S3.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 857.8 kB (52%)

Content Size

1.6 MB

After Optimization

790.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Myaccount2.orlandosentinel.com main page is 1.6 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. 45% of websites need less resources to load. Images take 786.1 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 82.0 kB

  • Original 92.2 kB
  • After minification 87.8 kB
  • After compression 10.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 82.0 kB or 89% of the original size.

Image Optimization

-25%

Potential reduce by 194.0 kB

  • Original 786.1 kB
  • After minification 592.1 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, Myaccount 2 Orlando Sentinel needs image optimization as it can save up to 194.0 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-74%

Potential reduce by 448.0 kB

  • Original 606.7 kB
  • After minification 551.7 kB
  • After compression 158.7 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 448.0 kB or 74% of the original size.

CSS Optimization

-82%

Potential reduce by 133.7 kB

  • Original 163.0 kB
  • After minification 126.6 kB
  • After compression 29.3 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. Myaccount2.orlandosentinel.com needs all CSS files to be minified and compressed as it can save up to 133.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 34 (64%)

Requests Now

53

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

myaccount2.orlandosentinel.com

myaccount2.orlandosentinel.com

42 ms

myaccount2.orlandosentinel.com

myaccount2.orlandosentinel.com

99 ms

main.css

main.css

60 ms

jquery-ui-1.10.3.custom.min.css

jquery-ui-1.10.3.custom.min.css

71 ms

jquery.min.js

jquery.min.js

80 ms

knockout-3.0.0.js

knockout-3.0.0.js

69 ms

koExternalTemplateEngine_all.min.js

koExternalTemplateEngine_all.min.js

69 ms

Classes.js

Classes.js

75 ms

bindingHint.js

bindingHint.js

73 ms

MenuViewModel.js

MenuViewModel.js

75 ms

IndexViewModel.js

IndexViewModel.js

74 ms

flexslider.css

flexslider.css

75 ms

jquery.easing.js

jquery.easing.js

74 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

97 ms

jquery.waitforimages.js

jquery.waitforimages.js

96 ms

jquery.slideshow.js

jquery.slideshow.js

94 ms

functions.js

functions.js

95 ms

class.application.js

class.application.js

96 ms

console.log.js

console.log.js

99 ms

jquery-ui-1.10.3.custom.min.js

jquery-ui-1.10.3.custom.min.js

144 ms

jQuery.equalHeights.js

jQuery.equalHeights.js

100 ms

apprise-v2.min.js

apprise-v2.min.js

99 ms

subcon.js

subcon.js

100 ms

jquery.cookie.js

jquery.cookie.js

99 ms

omniture.js

omniture.js

109 ms

tooltip.js

tooltip.js

99 ms

custom-main.js

custom-main.js

104 ms

SubconMaster.Functions.js

SubconMaster.Functions.js

105 ms

SubconMaster.Load.js

SubconMaster.Load.js

104 ms

SubconMaster.Events.js

SubconMaster.Events.js

106 ms

mobile.css

mobile.css

113 ms

custom.css

custom.css

119 ms

custom.css.map

custom.css.map

113 ms

custom.less

custom.less

124 ms

custom.min.css

custom.min.css

124 ms

WebResource.axd

WebResource.axd

177 ms

ScriptResource.axd

ScriptResource.axd

164 ms

ScriptResource.axd

ScriptResource.axd

122 ms

orlnews-mg2.js

orlnews-mg2.js

223 ms

burgermenu.png

burgermenu.png

100 ms

menu-Item.html

menu-Item.html

111 ms

OS_NGUX_Welcome_963x314_OS.jpg

OS_NGUX_Welcome_963x314_OS.jpg

242 ms

slideshow.xml

slideshow.xml

145 ms

favicon.ico

favicon.ico

131 ms

largeLoader.png

largeLoader.png

130 ms

bg-footer-callout.png

bg-footer-callout.png

117 ms

OS_NGUX_SignUp_963x314_OS.jpg

OS_NGUX_SignUp_963x314_OS.jpg

245 ms

orlando_main_ezpay.jpg

orlando_main_ezpay.jpg

176 ms

orlando_main_deliveryissue.jpg

orlando_main_deliveryissue.jpg

203 ms

orlando_main_vacation.jpg

orlando_main_vacation.jpg

247 ms

OSMEDIAGROUPLOGOS_CMYK.png

OSMEDIAGROUPLOGOS_CMYK.png

195 ms

facebook.png

facebook.png

193 ms

twitter.png

twitter.png

207 ms

instagram-logo.png

instagram-logo.png

246 ms

bg_control_nav.png

bg_control_nav.png

10 ms

slider-arrows.png

slider-arrows.png

14 ms

Accessibility Review

myaccount2.orlandosentinel.com accessibility score

77

Accessibility Issues

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

Buttons do not have an accessible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

myaccount2.orlandosentinel.com best practices score

67

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

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

myaccount2.orlandosentinel.com SEO score

62

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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Myaccount2.orlandosentinel.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Myaccount2.orlandosentinel.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

myaccount2.orlandosentinel.com

Open Graph description is not detected on the main page of Myaccount 2 Orlando Sentinel. 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: