1.4 sec in total
24 ms
1.2 sec
209 ms
Click here to check amazing Drudge content for United States. Otherwise, check out these important facts you probably never knew about drudge.com
Headlines: Sleepy Don; An Unexpected Player in Israel's Defense: Jordan, Home to Many Palestinians; SCOTUS Deals Massive Blow to Right to Protest; Truth Social Backers Baffled by Stock Woes; Elon
Visit drudge.comWe analyzed Drudge.com page load time and found that the first response time was 24 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
drudge.com performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value2.9 s
81/100
25%
Value6.2 s
44/100
10%
Value1,380 ms
16/100
30%
Value0.795
5/100
15%
Value13.4 s
11/100
10%
24 ms
212 ms
135 ms
114 ms
33 ms
Our browser made a total of 66 requests to load all elements on the main page. We found that 15% of them (10 requests) were addressed to the original Drudge.com, 12% (8 requests) were made to Tpc.googlesyndication.com and 12% (8 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (348 ms) relates to the external source Googleads.g.doubleclick.net.
Page size can be reduced by 228.8 kB (46%)
500.2 kB
271.4 kB
In fact, the total size of Drudge.com main page is 500.2 kB. 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 290.9 kB which makes up the majority of the site volume.
Potential reduce by 31.6 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 31.6 kB or 74% of the original size.
Potential reduce by 2.8 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.
Potential reduce by 183.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 183.6 kB or 63% of the original size.
Potential reduce by 10.7 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 10.7 kB or 81% of the original size.
Number of requests can be reduced by 36 (60%)
60
24
The browser has sent 60 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 26 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
drudge.com
24 ms
www.drudge.com
212 ms
frontstyle.css
135 ms
blogads-feed-css
114 ms
jquery.min.js
33 ms
show_ads.js
8 ms
blogads-feed-js
145 ms
urchin.js
18 ms
gpt.js
53 ms
plusone.js
160 ms
ca-pub-8378161688790357.js
61 ms
zrt_lookup.html
61 ms
show_ads_impl.js
59 ms
branding.css
48 ms
retort
112 ms
logosmall.gif
106 ms
google-button.gif
105 ms
my-yahoo-button.gif
105 ms
rss-icon.png
106 ms
advertise-liberally.gif
183 ms
poweredby_FFFFFF.gif
109 ms
pubads_impl_81.js
16 ms
container.html
11 ms
branding.css
90 ms
ads
194 ms
osd.js
28 ms
ads
348 ms
cb=gapi.loaded_0
103 ms
ads
121 ms
ads
145 ms
ads
264 ms
57 ms
img.jpg
65 ms
c.gif
37 ms
put_trade_desk_img_tag.js
132 ms
abg.js
33 ms
m_js_controller.js
35 ms
blogads-tweet-this-button.png
72 ms
favicon
139 ms
s
22 ms
googlelogo_color_112x36dp.png
132 ms
nessie_icon_tiamat_white.png
17 ms
x_button_blue2.png
55 ms
audience_segments_and_tracking_tags_pairs.js
129 ms
book_excerpt_feature_get_segments_cookie_new.php
103 ms
__utm.gif
47 ms
quant.js
41 ms
ads
259 ms
cb=gapi.loaded_1
82 ms
fastbutton
239 ms
pixel;r=1963347342;a=p-wjyLwX_bEPD_-;fpan=1;fpa=P0-207444879-1456753494921;ns=0;ce=1;cm=;je=0;sr=1024x768x32;enc=n;dst=0;et=1456753494920;tzo=-180;ref=;url=http%3A%2F%2Fwww.drudge.com%2F;ogl=
50 ms
6053807205279076498
47 ms
16759540961872689411
44 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
49 ms
blank.gif
46 ms
postmessageRelay
144 ms
cb=gapi.loaded_0
36 ms
cb=gapi.loaded_1
24 ms
000000_new_ico.gif
17 ms
api.js
49 ms
core:rpc:shindig.random:shindig.sha1.js
70 ms
2536007149-postmessagerelay.js
52 ms
grlryt2bdKIyfMSOhzd1eA.woff
88 ms
generic160.css
83 ms
getQuestions
83 ms
ui
39 ms
drudge.com accessibility score
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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
drudge.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
drudge.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
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.
drudge.com
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: