2.1 sec in total
544 ms
1.4 sec
174 ms
Welcome to drush.org homepage info - get ready to check Drush best content for United States right away, or after learning these important things about drush.org
Visit drush.orgWe analyzed Drush.org page load time and found that the first response time was 544 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.
drush.org performance score
name
value
score
weighting
Value2.9 s
54/100
10%
Value4.8 s
31/100
25%
Value2.9 s
95/100
10%
Value280 ms
80/100
30%
Value0.306
38/100
15%
Value4.1 s
87/100
10%
544 ms
41 ms
23 ms
87 ms
47 ms
Our browser made a total of 31 requests to load all elements on the main page. We found that 39% of them (12 requests) were addressed to the original Drush.org, 16% (5 requests) were made to Poser.pugx.org and 13% (4 requests) were made to Media.readthedocs.org. The less responsive or slowest element that took the longest time to load (544 ms) belongs to the original domain Drush.org.
Page size can be reduced by 348.1 kB (64%)
540.7 kB
192.7 kB
In fact, the total size of Drush.org main page is 540.7 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. 35% of websites need less resources to load. Javascripts take 426.6 kB which makes up the majority of the site volume.
Potential reduce by 10.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. This page needs HTML code to be minified as it can gain 2.6 kB, which is 18% 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 10.7 kB or 74% of the original size.
Potential reduce by 257.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 257.6 kB or 60% of the original size.
Potential reduce by 79.8 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. Drush.org needs all CSS files to be minified and compressed as it can save up to 79.8 kB or 80% of the original size.
Number of requests can be reduced by 18 (86%)
21
3
The browser has sent 21 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Drush. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
drush.org
544 ms
www.drush.org.
41 ms
23 ms
css
87 ms
theme.css
47 ms
theme_extra.css
46 ms
highlight.css
6 ms
badge_only.css
64 ms
readthedocs-doc-embed.css
67 ms
jquery-2.1.1.min.js
51 ms
modernizr-2.8.3.min.js
44 ms
highlight.pack.js
51 ms
theme.js
49 ms
readthedocs-data.js
60 ms
readthedocs-dynamic-include.js
49 ms
readthedocs-doc-embed.js
63 ms
ga.js
41 ms
stable.png
349 ms
176 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
99 ms
DvlFBScY1r-FMtZSYIYoYw.ttf
118 ms
fontawesome_webfont.woff
36 ms
fontawesome-webfont.woff
32 ms
dazS1PrQQuCxC3iOAJFEJZ_TkvowlIOtbR7ePgFOpF4.ttf
131 ms
y7lebkjgREBJK96VQi37Zp0EAVxt0G0biEntp43Qt6E.ttf
132 ms
__utm.gif
18 ms
__utm.gif
27 ms
stable
260 ms
downloads
238 ms
unstable
245 ms
license
240 ms
drush.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Links do not have a discernible name
drush.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Page has valid source maps
drush.org 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
N/A
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Drush.org 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 Drush.org 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.
drush.org
Open Graph description is not detected on the main page of Drush. 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: