7.4 sec in total
1.1 sec
5.8 sec
507 ms
Click here to check amazing Atn To content for Brazil. Otherwise, check out these important facts you probably never knew about atn.to.gov.br
Visit atn.to.gov.brWe analyzed Atn.to.gov.br page load time and found that the first response time was 1.1 sec and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
atn.to.gov.br performance score
name
value
score
weighting
Value2.4 s
72/100
10%
Value3.2 s
71/100
25%
Value7.0 s
32/100
10%
Value0 ms
100/100
30%
Value0.045
99/100
15%
Value2.4 s
99/100
10%
1136 ms
2475 ms
38 ms
21 ms
18 ms
Our browser made a total of 143 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Atn.to.gov.br, 17% (24 requests) were made to Static.xx.fbcdn.net and 13% (18 requests) were made to Pbs.twimg.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Secom.to.gov.br.
Page size can be reduced by 905.6 kB (36%)
2.5 MB
1.6 MB
In fact, the total size of Atn.to.gov.br main page is 2.5 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 1.4 MB which makes up the majority of the site volume.
Potential reduce by 18.7 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.7 kB, which is 23% 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 18.7 kB or 77% of the original size.
Potential reduce by 51.4 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. Atn To images are well optimized though.
Potential reduce by 594.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 594.6 kB or 75% of the original size.
Potential reduce by 241.0 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. Atn.to.gov.br needs all CSS files to be minified and compressed as it can save up to 241.0 kB or 83% of the original size.
Number of requests can be reduced by 61 (44%)
138
77
The browser has sent 138 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Atn To. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
atn.to.gov.br
1136 ms
secom.to.gov.br
2475 ms
css
38 ms
bootstrap.min.css
21 ms
blueimp-gallery.min.css
18 ms
styles.css
219 ms
topo.js
448 ms
pub.php
339 ms
jquery.min.js
17 ms
jquery.scroll4ever.min.js
31 ms
bootstrap.min.js
30 ms
jquery.blueimp-gallery.min.js
32 ms
scripts.js
490 ms
buttons.js
28 ms
base.js
490 ms
241466_190.jpg
464 ms
266623_340x250.jpg
653 ms
266611_340x250.jpg
626 ms
264351_340x250.jpg
629 ms
268065_200x130.jpg
353 ms
268060_200x130.jpg
625 ms
268051_200x130.jpg
625 ms
268052_200x130.jpg
650 ms
268041_200x130.jpg
690 ms
241464_190.jpg
688 ms
241461_190.jpg
687 ms
241462_190.jpg
685 ms
241465_190.jpg
789 ms
253952_190.jpg
788 ms
268055_300.jpg
1040 ms
topo.php
400 ms
analytics.js
42 ms
pub_image.php
733 ms
facebook.png
447 ms
twitter.png
492 ms
ODelI1aHBYDBqgeIAH2zlBM0YzuT7MdOe03otPbuUS0.woff
79 ms
widgets.js
85 ms
grid.php
343 ms
collect
34 ms
collect
26 ms
instagram.png
696 ms
tocantins_tv.png
788 ms
tocantins_noar.png
787 ms
likebox.php
334 ms
glyphicons-halflings-regular.woff
21 ms
base.php
264 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
209 ms
getAllAppDefault.esi
98 ms
sprite.png
1302 ms
logo.png
672 ms
bootstrap.min.css
172 ms
style.css
231 ms
jquery.js
661 ms
roNeOY-tz5Y.css
161 ms
UHhaxo8Cs3k.css
194 ms
O8DK6hTywHD.css
242 ms
Qz9nHTUX1Wv.css
285 ms
_rx8naC75Dy.js
349 ms
x5F9OMjKyLw.js
371 ms
ICDbTSzjQEg.js
277 ms
TTCre3391I0.js
276 ms
C-h3nYPqETO.js
275 ms
rFmE1g6Dkoz.js
411 ms
7cm7D75Y0Sf.js
400 ms
oRoBXlHCpEy.js
369 ms
336JejShbZp.js
393 ms
sj-JwAJi4AH.js
402 ms
DKRU1bYTkTw.js
401 ms
ZNPAadQNc33.js
400 ms
W0OV23mIOyO.js
399 ms
36TdwhIHusi.js
403 ms
getSegment.php
205 ms
checkOAuth.esi
46 ms
syndication
297 ms
334370271567945728
297 ms
ga.js
62 ms
12798110_1012628945462970_1513761198_n.jpg
570 ms
play_small.png
171 ms
12748295_950248128394415_901389162_n.jpg
709 ms
12798118_1716286085253068_1803115749_n.jpg
792 ms
12797638_1092622634129124_1466618743_n.jpg
783 ms
12725067_944087032379429_273042972_n.jpg
772 ms
12783257_1638146983113270_1828952443_n.jpg
802 ms
t.dhj
75 ms
__utm.gif
309 ms
12799076_983923814989064_5686503659152800994_n.jpg
411 ms
12806033_983923704989075_2040851329602422209_n.png
464 ms
12144720_732507296879908_2609112231811680303_n.jpg
484 ms
12510374_569269726554694_6830534382779498783_n.jpg
491 ms
11227938_953181768107121_2481848551372340435_n.jpg
484 ms
996774_914955501915725_144931206697597626_n.jpg
487 ms
12715466_10204316484031331_1818401620736657285_n.jpg
491 ms
12552622_937001966406940_1214053472954026139_n.jpg
498 ms
12510372_890705511042838_2478245043567114587_n.jpg
496 ms
12743562_805068859622842_9208409909174896701_n.jpg
499 ms
12246992_879166585531953_1598102719831738392_n.jpg
525 ms
12592492_565935690223411_3918944095921683543_n.jpg
499 ms
12803303_778200665646123_4482102927329412613_n.jpg
503 ms
HEyyDkPknAC.png
215 ms
wL6VQj7Ab77.png
215 ms
s7jcwEQH7Sx.png
214 ms
t.dhj
189 ms
1f60a.png
323 ms
pUFVdPjIRct.png
62 ms
1f692.png
198 ms
1f449.png
197 ms
1f603.png
196 ms
1f604.png
207 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
59 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
163 ms
cm
139 ms
BRZnAhta_normal.jpg
186 ms
eT4rZcg7_normal.jpg
148 ms
Ccc5RodW8AANbk6.jpg:large
190 ms
CceEONzUUAETgRt.jpg
154 ms
CceD4swUcAASI63.jpg
161 ms
CcduAHlUkAAeyFW.jpg
163 ms
CcdqFA5WEAM8B4z.jpg
162 ms
CcdppVmXEAETWSi.jpg
164 ms
CcdmWX8WwAAgAnC.jpg
170 ms
Ccdlit9WoAAhPYK.jpg
170 ms
CcdkucLWwAA-6Ir.jpg
169 ms
CcddDIHXIAA5GmO.jpg
211 ms
CcdVvSaW0AEn7LI.jpg
217 ms
CcdReuTWEAA8zlR.jpg
217 ms
CcaJOWrWAAQQBlY.jpg
172 ms
CcaIU-iXIAEatyn.jpg
174 ms
CcaHmD9WIAEUEXF.jpg
186 ms
CcZ8ytGUkAAA3Wf.jpg
217 ms
hbpix
43 ms
s-3271.xgi
27 ms
47 ms
15 ms
52154.gif
16 ms
pixel
25 ms
2981
18 ms
jot
53 ms
I6-MnjEovm5.js
24 ms
vlXaquuXMrr.js
18 ms
index.2d85e55d89f85ae69e4f2ca5ab9438b7.html
30 ms
buttons.ab966a004186897711de4a5ed256c924.css
13 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
8 ms
st.1188278743c14064d5e8ae56c8ada29c.js
7 ms
atn.to.gov.br accessibility score
atn.to.gov.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
atn.to.gov.br SEO score
PT
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Atn.to.gov.br 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 Atn.to.gov.br main page’s claimed encoding is . 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.
atn.to.gov.br
Open Graph description is not detected on the main page of Atn To. 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: