5.1 sec in total
712 ms
4 sec
350 ms
Visit docerar.pt now to see the best up-to-date Doce RAR content and also check out these interesting facts you probably never knew about docerar.pt
Mais de 200 doces receitas com açúcar RAR. Conheça os nossos produtos e promoções.
Visit docerar.ptWe analyzed Docerar.pt page load time and found that the first response time was 712 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
docerar.pt performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value50.5 s
0/100
25%
Value13.3 s
2/100
10%
Value700 ms
42/100
30%
Value0.025
100/100
15%
Value23.6 s
1/100
10%
712 ms
232 ms
238 ms
237 ms
348 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 98% of them (81 requests) were addressed to the original Docerar.pt, 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Docerar.pt.
Page size can be reduced by 1.8 MB (69%)
2.7 MB
826.5 kB
In fact, the total size of Docerar.pt main page is 2.7 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. 55% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 26.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 26.8 kB or 80% of the original size.
Potential reduce by 1.0 MB
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, Doce RAR needs image optimization as it can save up to 1.0 MB or 60% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 744.2 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 744.2 kB or 85% of the original size.
Potential reduce by 29.1 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. Docerar.pt needs all CSS files to be minified and compressed as it can save up to 29.1 kB or 85% of the original size.
Number of requests can be reduced by 41 (50%)
82
41
The browser has sent 82 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Doce RAR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
docerar.pt
712 ms
site.css
232 ms
winter.css
238 ms
calendar.css
237 ms
yahoo-dom-event.js
348 ms
site.js
354 ms
cmsajax.js
346 ms
datafuncs.js
460 ms
swfobject.js
359 ms
yahoo.js
476 ms
event.js
611 ms
dom.js
600 ms
calendar.js
816 ms
yahoo-dom-event.js
604 ms
calendar-min.js
699 ms
xmlhttprequest.js
595 ms
utils.js
826 ms
calendar.js
851 ms
calendar-setup.js
836 ms
calendar-pt.js
885 ms
prototype.js
947 ms
scriptaculous.js
949 ms
renderTTF.js
951 ms
Gmap.js
956 ms
datafuncs.php
998 ms
layout-2d.css
926 ms
slider.js
127 ms
rubTL_37.png
565 ms
rubTL2_37.png
448 ms
rubTL_69.png
456 ms
rubTL2_69.png
450 ms
rubTL_70.png
348 ms
rubTL2_70.png
341 ms
rubTL_115.png
571 ms
rubTL2_115.png
578 ms
rubTL_86.png
679 ms
rubTL2_86.png
680 ms
rubTL_87.png
684 ms
rubTL2_87.png
792 ms
rubTL_114.png
911 ms
rubTL2_114.png
808 ms
fundo_home3.jpg
1126 ms
natal.png
908 ms
TTF_33d722df816c3bb2a5fb0099abea444e
806 ms
TTF_df09453824c791f2dd085a6a2bf706b8
913 ms
TTF_c6f0a0494c263daf15559a44e527e6c2
929 ms
TTF_f8b2a9edafe18ccc0a21459f2a15c90a
949 ms
TTF_c498a2b0d5401e57b299d738e2f0e417
1029 ms
TTF_b59f20efba06a1be8a5071eae877ff2c
1035 ms
TTF_3479c79eadd8329a34afff3897239e7c
1035 ms
TTF_23c052d0e57279c49d514381a4c7b272
1050 ms
login2.png
1177 ms
tit_newsl_home.png
1258 ms
tpt.gif
1159 ms
destaque.jpg
1263 ms
btnver.jpg
1171 ms
receitahome.png
1245 ms
barr_sep_rec_home.jpg
1280 ms
btnverhome.jpg
1295 ms
submenu_topo.png
1405 ms
TTFP_7c2cacd21176f79a325125a7c31e7785
1368 ms
TTFP_4b47c3fdd65012ba96530b4a5ab40eb8
1379 ms
TTFP_873b0b326370e15ddd78781f693226a2
1378 ms
ga.js
5 ms
__utm.gif
12 ms
TTFP_624de0574de7a910e2652dced291dadd
1069 ms
TTFP_f1aed1aa04a9f034e84ffad0a7dc0527
1077 ms
TTFP_59dbd64ee537b10b07a19ea80fbe7648
1052 ms
TTFP_865bca62a5af9870eaf7143a595d7b5b
1060 ms
TTFP_7fd1f542c365e4e3ebd1b88de7b77853
1063 ms
TTFP_51643bcebb6ae66524fddbf8af077336
970 ms
TTFP_c3d52328d10d4ba1dcc3a52a81278cd2
965 ms
TTFP_58482a1269d51c1f43cb0aa12c96cd0e
970 ms
TTFP_4c46b5eb8f0e8b0e9540f0d4b8945991
942 ms
TTFP_f55f8b8bd9efaeb4466080e6dd779e9c
953 ms
TTFP_1b6b15427e275ea3f40c43fa828a2080
957 ms
TTFP_0df9b38bbb543c29abc2d7768e66fdfd
866 ms
logorar.png
954 ms
fundo_login.png
966 ms
btnsubhome.jpg
834 ms
bombom_home.png
950 ms
btnok.jpg
851 ms
fundo_menu.png
1066 ms
docerar.pt 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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
docerar.pt 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
docerar.pt SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
PT
N/A
WINDOWS-1252
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Docerar.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Docerar.pt main page’s claimed encoding is windows-1252. 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.
docerar.pt
Open Graph description is not detected on the main page of Doce RAR. 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: