Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

drudge.com

Drudge Retort: The Other Side of the News

Page Load Speed

2 sec in total

First Response

45 ms

Resources Loaded

1.8 sec

Page Rendered

147 ms

drudge.com screenshot

About Website

Click here to check amazing Drudge content for United States. Otherwise, check out these important facts you probably never knew about drudge.com

Headlines: Trump Picks RFK Jr for HHS Secretary; Jake Paul Beats Mikes Tyson by Decision; Muslims Voted Trump, Now Upset by Pro-Israel Cabinet Picks; Ramaswarmy Suggests Cutting Veterans' Health

Visit drudge.com

Key Findings

We analyzed Drudge.com page load time and found that the first response time was 45 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

drudge.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

85/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value3,210 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.795

5/100

15%

TTI (Time to Interactive)

Value15.0 s

7/100

10%

Network Requests Diagram

drudge.com

45 ms

drudge.com

28 ms

frontstyle.css

3 ms

jquery.min.js

27 ms

adsbygoogle.js

166 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 9% of them (5 requests) were addressed to the original Drudge.com, 18% (10 requests) were made to Googleads.g.doubleclick.net and 16% (9 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (769 ms) relates to the external source Developers.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 100.1 kB (10%)

Content Size

1.0 MB

After Optimization

944.0 kB

In fact, the total size of Drudge.com main page is 1.0 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. 60% of websites need less resources to load. Javascripts take 858.7 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 60.0 kB

  • Original 74.7 kB
  • After minification 73.9 kB
  • After compression 14.7 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 60.0 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 55 B

  • Original 105.2 kB
  • After minification 105.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. Drudge images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 35.8 kB

  • Original 858.7 kB
  • After minification 858.7 kB
  • After compression 822.9 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.

CSS Optimization

-77%

Potential reduce by 4.3 kB

  • Original 5.5 kB
  • After minification 4.4 kB
  • After compression 1.2 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. Drudge.com needs all CSS files to be minified and compressed as it can save up to 4.3 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (62%)

Requests Now

50

After Optimization

19

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

Accessibility Review

drudge.com accessibility score

70

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

drudge.com best practices score

50

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

drudge.com SEO score

86

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

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Drudge.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 Drudge.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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