Tools & Wizards About Us
secure.charlotteobserver.com screenshot

Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

secure.charlotteobserver.com

Charlotte Breaking News, Sports & Crime | Charlotte Observer

Page Load Speed

7.7 sec in total

First Response

220 ms

Resources Loaded

1.4 sec

Page Rendered

6.1 sec

secure.charlotteobserver.com screenshot

About Website

Click here to check amazing Secure Charlotte Observer content for United States. Otherwise, check out these important facts you probably never knew about secure.charlotteobserver.com

Read today's latest news headlines from Charlotte and North Carolina. Stay up to date on local business, sports, crime, politics, arts, culture, and more.

Visit secure.charlotteobserver.com

Key Findings

We analyzed Secure.charlotteobserver.com page load time and found that the first response time was 220 ms and then it took 7.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

secure.charlotteobserver.com performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.8 s

0/100

25%

SI (Speed Index)

Value69.4 s

0/100

10%

TBT (Total Blocking Time)

Value99,670 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.347

32/100

15%

TTI (Time to Interactive)

Value139.0 s

0/100

10%

Network Requests Diagram

secure.charlotteobserver.com

220 ms

www.charlotteobserver.com

116 ms

charlotteobservercore.js

70 ms

vendor.bundle-e8bf89b42a8198ff411c.js

111 ms

mi-header.bundle-607fd7cfea582dcf340d.js

81 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Secure.charlotteobserver.com, 73% (36 requests) were made to Charlotteobserver.com and 4% (2 requests) were made to Heraldonline.com. The less responsive or slowest element that took the longest time to load (701 ms) relates to the external source Heraldonline.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 404.9 kB (28%)

Content Size

1.5 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Secure.charlotteobserver.com main page is 1.5 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. 70% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 203.6 kB

  • Original 224.5 kB
  • After minification 100.4 kB
  • After compression 20.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 124.0 kB, which is 55% 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 203.6 kB or 91% of the original size.

Image Optimization

-16%

Potential reduce by 201.2 kB

  • Original 1.2 MB
  • After minification 1.0 MB

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, Secure Charlotte Observer needs image optimization as it can save up to 201.2 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 51 B

  • Original 9.6 kB
  • After minification 9.6 kB
  • After compression 9.6 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. This website has mostly compressed JavaScripts.

Requests Breakdown

Number of requests can be reduced by 13 (28%)

Requests Now

46

After Optimization

33

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

secure.charlotteobserver.com

secure.charlotteobserver.com

220 ms

www.charlotteobserver.com

www.charlotteobserver.com

116 ms

charlotteobservercore.js

charlotteobservercore.js

70 ms

vendor.bundle-e8bf89b42a8198ff411c.js

vendor.bundle-e8bf89b42a8198ff411c.js

111 ms

mi-header.bundle-607fd7cfea582dcf340d.js

mi-header.bundle-607fd7cfea582dcf340d.js

81 ms

css

css

109 ms

mi-styles.edbcba0a9d4e3d9d95fb.css

mi-styles.edbcba0a9d4e3d9d95fb.css

173 ms

guid.js

guid.js

82 ms

api.js

api.js

378 ms

3240e224

3240e224

106 ms

mastheadPage.bundle-2a61125a3fda4d2d932e.js

mastheadPage.bundle-2a61125a3fda4d2d932e.js

102 ms

premium-topper.js

premium-topper.js

406 ms

mi-footer.bundle-9e59a31b822d120051b7.js

mi-footer.bundle-9e59a31b822d120051b7.js

159 ms

vue.bundle-eeca3ceab7d82993245e.js

vue.bundle-eeca3ceab7d82993245e.js

397 ms

videojs.bundle-243f8c7ebc265ae92f6e.js

videojs.bundle-243f8c7ebc265ae92f6e.js

399 ms

videoStory.bundle-ac8c70bb2ca8b9b54db5.js

videoStory.bundle-ac8c70bb2ca8b9b54db5.js

397 ms

footer.bundle-1f06f5f8ac3bfe589066.js

footer.bundle-1f06f5f8ac3bfe589066.js

395 ms

C5-logo-small.png

C5-logo-small.png

507 ms

logo-tab.svg

logo-tab.svg

701 ms

169F4EA8-813E-4572-A919-BB2F34734F97_1_105_c.jpeg

169F4EA8-813E-4572-A919-BB2F34734F97_1_105_c.jpeg

569 ms

Charlotte%20skyline

Charlotte%20skyline

604 ms

pre%20sc%20state%201.jpg

pre%20sc%20state%201.jpg

653 ms

093022_MIL_HER_FB_SW_103

093022_MIL_HER_FB_SW_103

571 ms

7ad6328e-8b3c-41b0-9ba1-8a36dbb417c2

7ad6328e-8b3c-41b0-9ba1-8a36dbb417c2

586 ms

jack-o-lanterns.jpg

jack-o-lanterns.jpg

592 ms

square-icon.svg

square-icon.svg

567 ms

logo.svg

logo.svg

329 ms

favicon-96.png

favicon-96.png

330 ms

logo.svg

logo.svg

332 ms

wxicons-blk-12.svg

wxicons-blk-12.svg

331 ms

20220929111702_5D4A6858.JPG

20220929111702_5D4A6858.JPG

330 ms

mmr_HurricaneIan_75.JPG

mmr_HurricaneIan_75.JPG

331 ms

als_Ian%20001.JPEG

als_Ian%20001.JPEG

373 ms

CLT_LatinoVote_001.JPG

CLT_LatinoVote_001.JPG

372 ms

CLT_Hornetsbk37.JPG

CLT_Hornetsbk37.JPG

371 ms

CLT_JS_JAMIE_DIMON_02

CLT_JS_JAMIE_DIMON_02

373 ms

Harris%20Teeter%20sign.jpg

Harris%20Teeter%20sign.jpg

371 ms

CLT_HORNETS_PRACTICE_05.JPG

CLT_HORNETS_PRACTICE_05.JPG

371 ms

CFG%20Cheri%20Beasley%20ad

CFG%20Cheri%20Beasley%20ad

621 ms

CLT_LatinoVote_005

CLT_LatinoVote_005

412 ms

TD%20bank

TD%20bank

562 ms

Siers1002-ONLINE.jpg

Siers1002-ONLINE.jpg

535 ms

WESLEY_WALLS_01.jpg

WESLEY_WALLS_01.jpg

411 ms

D3C50CD6-9E99-45C5-9248-124818EBA502.JPEG

D3C50CD6-9E99-45C5-9248-124818EBA502.JPEG

412 ms

IMG_4604.jpg

IMG_4604.jpg

567 ms

DSCF4939.jpg

DSCF4939.jpg

564 ms

favicon-32.png

favicon-32.png

560 ms

recaptcha__en.js

recaptcha__en.js

386 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

264 ms

Accessibility Review

secure.charlotteobserver.com accessibility score

81

Accessibility Issues

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

High

[aria-*] attributes are not valid or misspelled

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

High

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

secure.charlotteobserver.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the notification permission on page load

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

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

secure.charlotteobserver.com SEO score

77

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Secure.charlotteobserver.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Secure.charlotteobserver.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

secure.charlotteobserver.com

Open Graph description is not detected on the main page of Secure Charlotte Observer. 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: