1.9 sec in total
596 ms
1.3 sec
95 ms
Visit dunno.com now to see the best up-to-date Dunno content and also check out these interesting facts you probably never knew about dunno.com
Visit dunno.comWe analyzed Dunno.com page load time and found that the first response time was 596 ms and then it took 1.3 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.
dunno.com performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value5.5 s
19/100
25%
Value7.5 s
27/100
10%
Value900 ms
31/100
30%
Value0.009
100/100
15%
Value9.8 s
28/100
10%
596 ms
220 ms
232 ms
6 ms
8 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Dunno.com, 65% (35 requests) were made to Projecttimer.sourceforge.net and 7% (4 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (596 ms) belongs to the original domain Dunno.com.
Page size can be reduced by 27.1 kB (39%)
69.4 kB
42.3 kB
In fact, the total size of Dunno.com main page is 69.4 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. 30% of websites need less resources to load. Javascripts take 44.2 kB which makes up the majority of the site volume.
Potential reduce by 8.8 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 8.8 kB or 73% of the original size.
Potential reduce by 2.0 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. Obviously, Dunno needs image optimization as it can save up to 2.0 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 16.0 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 16.0 kB or 36% of the original size.
Potential reduce by 322 B
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. Dunno.com needs all CSS files to be minified and compressed as it can save up to 322 B or 59% of the original size.
Number of requests can be reduced by 44 (85%)
52
8
The browser has sent 52 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dunno. 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 as a result speed up the page load time.
dunno.com
596 ms
ProjectTimer.css
220 ms
ProjectTimer.js
232 ms
show_ads.js
6 ms
counter_xhtml.js
8 ms
urchin.js
5 ms
sflogo.php
76 ms
notifyIcon2.jpg
65 ms
PcFareMeter.png
75 ms
tl.png
134 ms
tr.png
133 ms
404040.ffffff.12.Features...png
134 ms
404040.ffffff.12.Screenshots...png
132 ms
404040.ffffff.12.Download...png
135 ms
404040.ffffff.12.Forum...png
135 ms
404040.ffffff.12.FAQ...png
135 ms
404040.ffffff.12.Development...png
135 ms
404040.ffffff.12.Summary...png
136 ms
bl.png
136 ms
br.png
138 ms
features.png
177 ms
Record%20Activities
147 ms
Auto%20move
151 ms
Groupings
151 ms
Auto%20save
165 ms
Hot%20Keys
164 ms
Export%20Import
176 ms
Trash%20bin
203 ms
FXcop
185 ms
ca-pub-3283881234559800.js
44 ms
zrt_lookup.html
46 ms
show_ads_impl.js
60 ms
t.png
172 ms
l.png
173 ms
c52829.ffffff.12.Features...png
240 ms
c52829.ffffff.12.Screenshots...png
240 ms
c52829.ffffff.12.Download...png
185 ms
c52829.ffffff.12.Forum...png
242 ms
c52829.ffffff.12.FAQ...png
195 ms
c52829.ffffff.12.Development...png
204 ms
c52829.ffffff.12.Summary...png
242 ms
r.png
226 ms
b.png
232 ms
t.php
95 ms
__utm.gif
13 ms
ads
206 ms
osd.js
4 ms
m_js_controller.js
28 ms
abg.js
47 ms
favicon
49 ms
googlelogo_color_112x36dp.png
38 ms
nessie_icon_tiamat_white.png
26 ms
s
20 ms
x_button_blue2.png
12 ms
dunno.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
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
dunno.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
dunno.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
EN
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dunno.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 Dunno.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.
dunno.com
Open Graph description is not detected on the main page of Dunno. 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: