5.6 sec in total
679 ms
3.9 sec
945 ms
Visit iolando.com.br now to see the best up-to-date Iolando content and also check out these interesting facts you probably never knew about iolando.com.br
Iolando Deputado Distrital - Defensor das Pessoas com Deficiência e a voz da Inclusão no Distrito Federal. Conheça as minhas realizações!
Visit iolando.com.brWe analyzed Iolando.com.br page load time and found that the first response time was 679 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
iolando.com.br performance score
name
value
score
weighting
Value5.7 s
5/100
10%
Value14.5 s
0/100
25%
Value13.3 s
2/100
10%
Value930 ms
30/100
30%
Value0
100/100
15%
Value17.4 s
4/100
10%
679 ms
142 ms
145 ms
146 ms
148 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 51% of them (62 requests) were addressed to the original Iolando.com.br, 12% (14 requests) were made to Fonts.gstatic.com and 10% (12 requests) were made to Khm1.googleapis.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Iolando.com.br.
Page size can be reduced by 1.1 MB (13%)
8.3 MB
7.2 MB
In fact, the total size of Iolando.com.br main page is 8.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 7.0 MB which makes up the majority of the site volume.
Potential reduce by 94.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 35.2 kB, which is 33% 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 94.4 kB or 88% of the original size.
Potential reduce by 112.7 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. Iolando images are well optimized though.
Potential reduce by 626.8 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 626.8 kB or 72% of the original size.
Potential reduce by 254.3 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. Iolando.com.br needs all CSS files to be minified and compressed as it can save up to 254.3 kB or 87% of the original size.
Number of requests can be reduced by 39 (37%)
105
66
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iolando. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 29 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
iolando.com.br
679 ms
rockox.css
142 ms
rockox-main.css
145 ms
animate.css
146 ms
pie-charts-style.css
148 ms
jquery.fancybox.css
147 ms
bootstrap.css
284 ms
revolution_style.css
228 ms
settings.css
228 ms
styles.css
236 ms
jquery.js
347 ms
jquery-migrate.min.js
244 ms
js
17 ms
jquery.js
38 ms
jquery.themepunch.plugins.min.js
302 ms
jquery.themepunch.revolution.min.js
311 ms
jquery.stellar.js
310 ms
custom.js
312 ms
jquery.jcarousel.min.js
339 ms
waypoints.js
365 ms
jquery.easypiechart.min.js
375 ms
nimble.js
416 ms
scrollspy.js
414 ms
jquery.fancybox.pack.js
416 ms
jquery.appear.js
416 ms
bootstrap.min.js
430 ms
counters.js
449 ms
jquery.form.min.js
477 ms
scripts.js
532 ms
css
24 ms
font-awesome.css
316 ms
logo.png
105 ms
thumb1.jpg
258 ms
women.png
446 ms
thumb3.jpg
616 ms
tablet.png
591 ms
service-sec-shadow.png
293 ms
table-bg.jpg
328 ms
10556396_789969691055449_9125088119802498682_n1-300x225.jpg
375 ms
10636202_789946571057761_8379598327410319660_n1-225x300.jpg
574 ms
10255221_282302535279005_2589575959715196122_n1-300x274.jpg
550 ms
Handshake1-300x153.jpg
585 ms
scrn-shot.png
1029 ms
portfolio1.jpg
755 ms
portfolio2.jpg
785 ms
portfolio3.jpg
850 ms
portfolio9.jpg
1374 ms
portfolio5.jpg
860 ms
portfolio4.jpg
1679 ms
portfolio12.jpg
1697 ms
portfolio11.jpg
1785 ms
portfolio10.jpg
1676 ms
portfolio7.jpg
1356 ms
portfolio8.jpg
1617 ms
10255221_282302535279005_2589575959715196122_n1.jpg
1649 ms
shirt4.jpg
1709 ms
f0c778f3d2be65eeb6af4daba2bdf5941.jpg
1746 ms
clients-bg.jpg
1768 ms
testi-pointer.png
1793 ms
10306079_714695101937001_2376789339494775971_n1-150x150.jpg
1874 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
40 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
41 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
43 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
41 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
40 ms
fontawesome-webfont.woff
1971 ms
PRmiXeptR36kaC0GEAetxrfB31yxOzP-czbf6AAKCVo.ttf
41 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
41 ms
PRmiXeptR36kaC0GEAetxi8cqLH4MEiSE0ROcU-qHOA.ttf
41 ms
PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf
41 ms
PRmiXeptR36kaC0GEAetxlDMrAYtoOisqqMDW9M_Mqc.ttf
41 ms
loader.gif
1751 ms
ajax-loader.gif
1769 ms
arrow_large_left.png
1338 ms
arrow_large_right.png
1375 ms
common.js
15 ms
map.js
15 ms
util.js
16 ms
marker.js
15 ms
infowindow.js
15 ms
onion.js
39 ms
css
16 ms
transparent.png
80 ms
ViewportInfoService.GetViewportInfo
57 ms
stats.js
54 ms
kh
53 ms
kh
50 ms
controls.js
35 ms
kh
98 ms
kh
87 ms
kh
84 ms
kh
84 ms
kh
82 ms
kh
90 ms
kh
100 ms
kh
100 ms
kh
95 ms
kh
102 ms
kh
168 ms
kh
87 ms
kh
86 ms
kh
92 ms
kh
99 ms
kh
84 ms
kh
92 ms
kh
97 ms
kh
94 ms
mapcnt6.png
81 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
69 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
71 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
71 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
71 ms
spotlight-poi.png
68 ms
google4.png
34 ms
sv5.png
31 ms
tmapctrl.png
16 ms
cb_scout5.png
16 ms
tmapctrl4.png
19 ms
imgs8.png
20 ms
google_white5.png
23 ms
AuthenticationService.Authenticate
264 ms
iolando.com.br 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
Form elements do not have associated labels
Links do not have a discernible name
iolando.com.br 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
iolando.com.br SEO score
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
Tap targets are not sized appropriately
PT
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iolando.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Iolando.com.br 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.
iolando.com.br
Open Graph description is not detected on the main page of Iolando. 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: