3.1 sec in total
358 ms
2 sec
738 ms
Click here to check amazing Distro Watch content for China. Otherwise, check out these important facts you probably never knew about distrowatch.com
News and feature lists of Linux and BSD distributions.
Visit distrowatch.comWe analyzed Distrowatch.com page load time and found that the first response time was 358 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
distrowatch.com performance score
name
value
score
weighting
Value4.8 s
12/100
10%
Value6.9 s
6/100
25%
Value10.7 s
7/100
10%
Value4,430 ms
0/100
30%
Value0.037
100/100
15%
Value21.4 s
1/100
10%
358 ms
189 ms
15 ms
40 ms
10 ms
Our browser made a total of 157 requests to load all elements on the main page. We found that 35% of them (55 requests) were addressed to the original Distrowatch.com, 7% (11 requests) were made to Contextual.media.net and 6% (9 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Distrowatch.com.
Page size can be reduced by 1.3 MB (21%)
6.3 MB
5.0 MB
In fact, the total size of Distrowatch.com main page is 6.3 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 4.6 MB which makes up the majority of the site volume.
Potential reduce by 144.4 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 21.9 kB, which is 12% 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 144.4 kB or 80% of the original size.
Potential reduce by 79.2 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. Distro Watch images are well optimized though.
Potential reduce by 942.5 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 942.5 kB or 68% of the original size.
Potential reduce by 145.4 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. Distrowatch.com needs all CSS files to be minified and compressed as it can save up to 145.4 kB or 84% of the original size.
Number of requests can be reduced by 78 (57%)
136
58
The browser has sent 136 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Distro Watch. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and as a result speed up the page load time.
distrowatch.com
358 ms
news.css
189 ms
brand
15 ms
nmedianet.js
40 ms
show_ads.js
10 ms
brand
32 ms
getads.js
417 ms
ga.js
49 ms
px.gif
27 ms
px.gif
27 ms
bping.php
22 ms
jstag
88 ms
rtbspub
117 ms
fcmdynet.js
60 ms
gpt.js
13 ms
dwbanner.png
111 ms
en.png
113 ms
es.png
237 ms
fr.png
239 ms
de.png
236 ms
pt.png
238 ms
lt.png
239 ms
jp.png
237 ms
pk.png
322 ms
wmhnetxjq
510 ms
xml.png
320 ms
xqipzgb
491 ms
bxolabzgha
319 ms
baruwa.png
427 ms
cyjscogzsj
406 ms
discountrue.png
410 ms
chameleonjohn.png
408 ms
porteuskiosk.png
496 ms
porteuskiosk-small.png
610 ms
skoi.png
498 ms
netrunner.png
507 ms
netrunner-small.png
686 ms
freebsd.png
582 ms
freebsd-small.png
848 ms
lxle.png
621 ms
lxle-small.png
1264 ms
rosa.png
688 ms
rosa-small.png
938 ms
xubuntu.png
696 ms
xubuntu-small.png
779 ms
pisi.png
778 ms
pisi-small.png
972 ms
tinycore.png
840 ms
tinycore-small.png
846 ms
webconverger.png
928 ms
checksync.php
31 ms
webconverger-small.png
1018 ms
__utm.gif
15 ms
pubads_impl_81.js
13 ms
usermatch
28 ms
container.html
26 ms
mediamain.html
64 ms
usermatch
19 ms
ca-pub-1979814992302941.js
125 ms
zrt_lookup.html
147 ms
show_ads_impl.js
72 ms
casale
42 ms
casale
54 ms
usersync.aspx
55 ms
53 ms
ecsync.php
40 ms
bping.php
32 ms
rtbspub
151 ms
fcmdynet.js
81 ms
abp.gif
35 ms
1
123 ms
abp.gif
31 ms
ubuntu.png
831 ms
abp.gif
22 ms
abp.gif
23 ms
ubuntu-small.png
986 ms
casale
20 ms
log.php
19 ms
csync.php
130 ms
pixel
87 ms
pixel
111 ms
crum
89 ms
crum
86 ms
crum
80 ms
rum
96 ms
acj
419 ms
ads
296 ms
mediamain.html
131 ms
osd.js
47 ms
rtbspub
123 ms
fcmdynet.js
45 ms
bping.php
22 ms
rum
22 ms
abp.gif
15 ms
acj
410 ms
abp.gif
13 ms
acj
468 ms
reactos.png
794 ms
reactos-small.png
901 ms
crum
15 ms
univention.png
835 ms
univention-small.png
1052 ms
emmabuntus.png
880 ms
emmabuntus-small.png
1116 ms
m
49 ms
mediamain.html
22 ms
crum
9 ms
getad
40 ms
nethserver.png
875 ms
nethserver-small.png
885 ms
pbxinaflash.png
887 ms
ads
253 ms
getad
39 ms
adown.png
875 ms
alevel.png
887 ms
ads
196 ms
aup.png
875 ms
tyephsnkwrbihcen
926 ms
js
75 ms
cqihdebblw
972 ms
szcwaloklwywfbh
882 ms
152986
51 ms
185595_us_cs_li_fy17q1w1_oa_why-refresh-nb-capture-orange_160x600_iip.jpg
155 ms
rud
28 ms
1095073168097863060
32 ms
abg.js
36 ms
m_js_controller.js
49 ms
js
67 ms
x_button_blue2.png
43 ms
googlelogo_dark_color_84x28dp.png
48 ms
s
26 ms
iconx2-000000.png
25 ms
152986
23 ms
googlelogo_dark_color_84x28dp.png
27 ms
185595_us_cs_li_fy17q1w1_oa_why-refresh-nb-capture-green_160x600_iip.jpg
76 ms
rud
56 ms
E4WYPs_lNJIuXrWpTsOcc3FIG36RfI0ERc0srw5QW9Y.js
5 ms
ads
228 ms
ads
237 ms
expansion_embed.js
9 ms
osd.js
17 ms
adj
59 ms
beacon
26 ms
firstevent
8 ms
rtblog.php
16 ms
timeline
17 ms
click
68 ms
lidar.js
15 ms
pixel
20 ms
push
22 ms
pixel
23 ms
pixel
23 ms
sd
48 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
56 ms
lidar.js
36 ms
pixel
23 ms
event
15 ms
distrowatch.com 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.
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
distrowatch.com 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
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
distrowatch.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Distrowatch.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 Distrowatch.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.
distrowatch.com
Open Graph description is not detected on the main page of Distro Watch. 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: