10.6 sec in total
1.4 sec
8.5 sec
729 ms
Click here to check amazing Cartao SUS content for Brazil. Otherwise, check out these important facts you probably never knew about cartaosus.com.br
⭐ Blog informativo sobre o Cartão SUS. Veja aqui tudo que você precisa saber sobre o cartão do SUS. Como fazer, segunda via, consultas e muito mais. ✅
Visit cartaosus.com.brWe analyzed Cartaosus.com.br page load time and found that the first response time was 1.4 sec and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
cartaosus.com.br performance score
name
value
score
weighting
Value1.6 s
94/100
10%
Value2.6 s
88/100
25%
Value10.0 s
9/100
10%
Value4,510 ms
0/100
30%
Value0.409
24/100
15%
Value22.8 s
1/100
10%
1373 ms
172 ms
27 ms
632 ms
317 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 18% of them (16 requests) were addressed to the original Cartaosus.com.br, 13% (12 requests) were made to Static.xx.fbcdn.net and 8% (7 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (6.4 sec) belongs to the original domain Cartaosus.com.br.
Page size can be reduced by 579.0 kB (36%)
1.6 MB
1.0 MB
In fact, the total size of Cartaosus.com.br main page is 1.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. 75% 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 794.3 kB which makes up the majority of the site volume.
Potential reduce by 37.5 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 37.5 kB or 75% of the original size.
Potential reduce by 19.1 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. Cartao SUS images are well optimized though.
Potential reduce by 263.1 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 263.1 kB or 57% of the original size.
Potential reduce by 259.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. Cartaosus.com.br needs all CSS files to be minified and compressed as it can save up to 259.4 kB or 84% of the original size.
Number of requests can be reduced by 58 (69%)
84
26
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cartao SUS. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 37 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
cartaosus.com.br
1373 ms
style.css
172 ms
css
27 ms
jquery.js
632 ms
jquery-migrate.min.js
317 ms
jquery.fitvids.js
317 ms
custom.js
319 ms
default.css
320 ms
adsbygoogle.js
12 ms
widgets.js
89 ms
plusone.js
79 ms
sharefront.js
317 ms
comment-reply.min.js
463 ms
wp-embed.min.js
463 ms
wp-emoji-release.min.js
286 ms
2824d2e936ea04436fdf11b1eec80459
102 ms
a5eef85d2facd0a0591369415a466b2b
101 ms
9e225001b2125326fd68d97ea588fc11
102 ms
gplus-32.png
28 ms
logo.jpg
261 ms
cartao_sus_novembro-1024x326.jpg
6433 ms
consulta-numero-nome-cartao-sus.jpg
523 ms
99b0e78a1e17706cda67b8e3184c9a08
118 ms
cbf2d5b1db27303982e756d72c7cfa6d
215 ms
63905b2b08cc51e20659b123f65c1a0d
247 ms
090f9155c6d8459db685e03726d0e2a7
212 ms
d291e42b8671ba56cb80848fcd733045
118 ms
d279412eacc418ff07643e855adb5794
213 ms
42f9c79e70872c1d63345c731b2cb3f9
212 ms
71ce19d1dc80c3f5eb697f4ba1edae0c
211 ms
sdk.js
20 ms
5t8vP9Hx2udzw372glmOxA.ttf
71 ms
ca-pub-2429586139936048.js
65 ms
zrt_lookup.html
69 ms
show_ads_impl.js
79 ms
376 ms
xd_arbiter.php
146 ms
xd_arbiter.php
408 ms
ads
334 ms
osd.js
265 ms
ads
389 ms
cb=gapi.loaded_0
353 ms
search.png
284 ms
top-btn.png
284 ms
like.php
270 ms
ads
614 ms
analytics.js
234 ms
button.831500944bc3eb7ea5276ccdc3f71d2e.js
219 ms
cb=gapi.loaded_1
171 ms
fastbutton
277 ms
rU2ubZ6l1Q5.js
168 ms
LVx-xkvaJ0b.png
235 ms
button.png
242 ms
5171746271700867932
100 ms
abg.js
131 ms
m_js_controller.js
161 ms
googlelogo_color_112x36dp.png
150 ms
collect
68 ms
A_Ufpzgs_8s
216 ms
like_box.php
86 ms
Fas0LsYw_Az.css
143 ms
QAAstqgzWat.css
136 ms
_rx8naC75Dy.js
144 ms
VcdofL9Z0wD.js
173 ms
0wM5s1Khldu.js
168 ms
TTCre3391I0.js
168 ms
postmessageRelay
273 ms
s
69 ms
x_button_blue2.png
86 ms
cb=gapi.loaded_0
187 ms
cb=gapi.loaded_1
156 ms
tweet_button.6a78875565a912489e9aef879c881358.en.html
180 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
216 ms
www-embed-player-vflQrT_sR.css
217 ms
www-embed-player.js
258 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
143 ms
10931241_846367858763749_5146188194956997800_n.jpg
130 ms
wL6VQj7Ab77.png
62 ms
s7jcwEQH7Sx.png
61 ms
api.js
80 ms
core:rpc:shindig.random:shindig.sha1.js
146 ms
2536007149-postmessagerelay.js
97 ms
I6-MnjEovm5.js
37 ms
f6T91Deal_q.js
41 ms
1eJU4PjErWSV5LNTKFXcze5UHikZLg3viIH581vcHWA.js
61 ms
ad_status.js
34 ms
jot
134 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
22 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
35 ms
cartaosus.com.br accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
[role]s are not contained by their required parent element
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
cartaosus.com.br 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
Browser errors were logged to the console
Page has valid source maps
cartaosus.com.br SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
PT
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cartaosus.com.br 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 Cartaosus.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.
cartaosus.com.br
Open Graph data is detected on the main page of Cartao SUS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: