Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

thedukereport.com

The Duke Report | All News is Made Up, Some of it is True.

Page Load Speed

30.2 sec in total

First Response

14.4 sec

Resources Loaded

15.1 sec

Page Rendered

754 ms

thedukereport.com screenshot

About Website

Click here to check amazing The Duke Report content for United States. Otherwise, check out these important facts you probably never knew about thedukereport.com

All News is made up, some of it is true. Aggregated sources from primary sources and evidence-based journalism sites.

Visit thedukereport.com

Key Findings

We analyzed Thedukereport.com page load time and found that the first response time was 14.4 sec and then it took 15.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

thedukereport.com performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

18/100

25%

SI (Speed Index)

Value2.2 s

99/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.474

18/100

15%

TTI (Time to Interactive)

Value4.2 s

86/100

10%

Network Requests Diagram

thedukereport.com

14388 ms

jquery.min.js

46 ms

cropped-Web-Site-Header-1080x138-1.png

59 ms

Cover-City-02.jpg

60 ms

autoptimize_23bd91167bc24bbdc6970162fc2aefab.js

28 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Thedukereport.com, 93% (28 requests) were made to Eadn-wc03-5744942.nxedge.io and 3% (1 request) were made to Static.cloudflareinsights.com. The less responsive or slowest element that took the longest time to load (14.4 sec) belongs to the original domain Thedukereport.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 142.2 kB (11%)

Content Size

1.2 MB

After Optimization

1.1 MB

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

HTML Optimization

-81%

Potential reduce by 142.2 kB

  • Original 176.5 kB
  • After minification 176.5 kB
  • After compression 34.3 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 142.2 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 1.0 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. The Duke Report images are well optimized though.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 47.3 kB
  • After minification 47.3 kB
  • After compression 47.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. Thedukereport.com has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

29

After Optimization

29

The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of The Duke Report. According to our analytics all requests are already optimized.

Accessibility Review

thedukereport.com accessibility score

97

Accessibility Issues

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

thedukereport.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

thedukereport.com SEO score

90

Search Engine Optimization Advices

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 Thedukereport.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 Thedukereport.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

Open Graph description is not detected on the main page of The Duke Report. 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: