5.3 sec in total
812 ms
4.3 sec
210 ms
Welcome to dape.net homepage info - get ready to check Dape best content right away, or after learning these important things about dape.net
Visit dape.netWe analyzed Dape.net page load time and found that the first response time was 812 ms and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
dape.net performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.074
95/100
15%
Value0
0/100
10%
812 ms
170 ms
1519 ms
373 ms
390 ms
Our browser made a total of 31 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Dape.net, 84% (26 requests) were made to Ww2.dape.net and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Ww2.dape.net.
Page size can be reduced by 6.9 kB (44%)
15.7 kB
8.9 kB
In fact, the total size of Dape.net main page is 15.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. Only 10% of websites need less resources to load. Javascripts take 7.9 kB which makes up the majority of the site volume.
Potential reduce by 227 B
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 227 B or 41% of the original size.
Potential reduce by 667 B
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, Dape needs image optimization as it can save up to 667 B or 31% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.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 1.6 kB or 20% of the original size.
Potential reduce by 4.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. Dape.net needs all CSS files to be minified and compressed as it can save up to 4.4 kB or 85% of the original size.
Number of requests can be reduced by 10 (33%)
30
20
The browser has sent 30 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Dape. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests and as a result speed up the page load time.
dape.net
812 ms
branco.html
170 ms
ww2.dape.net
1519 ms
style.css
373 ms
topo.html
390 ms
menu.html
395 ms
principal.html
355 ms
rodape.html
395 ms
canto1.gif
211 ms
logo_google.gif
228 ms
duvidas.gif
215 ms
ok.gif
241 ms
cinema.gif
590 ms
speedy.gif
515 ms
dape.gif
378 ms
antispam.gif
714 ms
canto2.gif
405 ms
bg2.png
387 ms
bg.png
525 ms
mostradata.js
567 ms
selo.php
329 ms
borda1.png
536 ms
seta_menu.gif
649 ms
gif01.png
685 ms
gif02.png
701 ms
envelope.jpg
728 ms
gif03.png
735 ms
urchin.js
23 ms
__utm.gif
13 ms
logo2.jpg
974 ms
br.gif
306 ms
dape.net accessibility score
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
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
dape.net best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
dape.net SEO score
N/A
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dape.net 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Dape.net 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.
dape.net
Open Graph description is not detected on the main page of Dape. 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: