4.8 sec in total
683 ms
3.6 sec
436 ms
Welcome to duploefeito.com homepage info - get ready to check Duplo Efeito best content right away, or after learning these important things about duploefeito.com
Conheça os nossos trabalhos com reportagem fotográfica. Somos a equipa perfeita para registrar o seu casamento.
Visit duploefeito.comWe analyzed Duploefeito.com page load time and found that the first response time was 683 ms and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
duploefeito.com performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value5.3 s
21/100
25%
Value6.0 s
46/100
10%
Value10 ms
100/100
30%
Value0.088
92/100
15%
Value5.0 s
76/100
10%
683 ms
25 ms
250 ms
198 ms
298 ms
Our browser made a total of 33 requests to load all elements on the main page. We found that 88% of them (29 requests) were addressed to the original Duploefeito.com, 9% (3 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Duploefeito.com.
Page size can be reduced by 456.4 kB (18%)
2.6 MB
2.1 MB
In fact, the total size of Duploefeito.com main page is 2.6 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. 30% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 13.1 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 5.4 kB, which is 34% 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 13.1 kB or 83% of the original size.
Potential reduce by 191.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. Duplo Efeito images are well optimized though.
Potential reduce by 171.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 171.6 kB or 74% of the original size.
Potential reduce by 79.9 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. Duploefeito.com needs all CSS files to be minified and compressed as it can save up to 79.9 kB or 85% of the original size.
Number of requests can be reduced by 17 (59%)
29
12
The browser has sent 29 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Duplo Efeito. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
duploefeito.com
683 ms
css
25 ms
prettyPhoto.css
250 ms
flexslider.css
198 ms
style.css
298 ms
layout.css
197 ms
camera.css
308 ms
color.css
205 ms
jquery-1.11.1.min.js
600 ms
jquery-migrate-1.2.1.min.js
332 ms
hoverIntent.js
332 ms
superfish.js
356 ms
supersubs.js
412 ms
tinynav.min.js
425 ms
custom.js
428 ms
jquery.flexslider-min.js
633 ms
camera.min.js
553 ms
jquery.prettyPhoto.js
517 ms
fade.js
524 ms
jquery-easing-1.3.js
533 ms
logo.png
680 ms
thumb-inicial.php
793 ms
thumb-inicial.php
936 ms
thumb-inicial.php
893 ms
pattern.png
387 ms
icon.png
436 ms
fb.png
476 ms
Q7EtAWlDLyjrIIFdmxKqN_esZW2xOQ-xsNqO47m55DA.ttf
27 ms
oCjlVB3OWc0D00Ervq8JG50EAVxt0G0biEntp43Qt6E.ttf
38 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
50 ms
camera-loader.gif
119 ms
2f1ecec5d1d36db10846c4a6ef26dbb6.jpg
1291 ms
1312ce0a5580acd0576d7e5a737fb6c6.jpg
954 ms
duploefeito.com 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
Links do not have a discernible name
duploefeito.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
General
Impact
Issue
Detected JavaScript libraries
duploefeito.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
PT
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Duploefeito.com can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it does not match the claimed English language. Our system also found out that Duploefeito.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.
duploefeito.com
Open Graph description is not detected on the main page of Duplo Efeito. 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: