6.2 sec in total
415 ms
5.6 sec
217 ms
Click here to check amazing Catho content for Brazil. Otherwise, check out these important facts you probably never knew about catho.com.br
Encontre aqui na Catho as melhores vagas de emprego. Temos mais de 150.000 vagas em todo o Brasil. Acesse a Catho e encontre a vaga perfeita pra você
Visit catho.com.brWe analyzed Catho.com.br page load time and found that the first response time was 415 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
catho.com.br performance score
name
value
score
weighting
Value3.3 s
41/100
10%
Value4.5 s
37/100
25%
Value10.8 s
7/100
10%
Value12,970 ms
0/100
30%
Value0.014
100/100
15%
Value25.3 s
0/100
10%
415 ms
2153 ms
280 ms
10 ms
223 ms
Our browser made a total of 145 requests to load all elements on the main page. We found that 6% of them (9 requests) were addressed to the original Catho.com.br, 15% (22 requests) were made to Static.catho.com.br and 6% (9 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Catho.com.br.
Page size can be reduced by 1.7 MB (62%)
2.7 MB
1.0 MB
In fact, the total size of Catho.com.br 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. 65% of websites need less resources to load. Javascripts take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 170.3 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 61.6 kB, which is 30% 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 170.3 kB or 83% of the original size.
Potential reduce by 32.0 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. Catho images are well optimized though.
Potential reduce by 1.0 MB
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 1.0 MB or 64% of the original size.
Potential reduce by 415.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. Catho.com.br needs all CSS files to be minified and compressed as it can save up to 415.0 kB or 85% of the original size.
Number of requests can be reduced by 83 (63%)
131
48
The browser has sent 131 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Catho. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and as a result speed up the page load time.
catho.com.br
415 ms
www.catho.com.br
2153 ms
1d078d8b4998f58c231d27a1b18852a9.css
280 ms
satelliteLib-2f106bf484e723e4f69c909a108a726c138ed753.js
10 ms
97f77e60804b764dd2a32bf41467bcbd.js
223 ms
25063191cc23541e8f0a325af062d938.js
222 ms
be7f4544b77ac3b019b1637cd768c1e6.js
252 ms
googleTagManagerControl.js
123 ms
googleTagManagerEvents.js
124 ms
clickheat.js
830 ms
s_code.js
558 ms
s-code-contents-bc44ca2649573d5392d3eeb72aa25a8019f23d0a.js
42 ms
1385 ms
81 ms
google_play.png
278 ms
app_store.png
278 ms
logoCathoB2c.svg
78 ms
spriteFuncaoTop.png
55 ms
sprite.png
87 ms
spriteHomeB2C.png
79 ms
mapa_brasil.png
77 ms
curriculoEficiente.jpg
84 ms
prepareseEntrevistas.jpg
85 ms
curriculoAtraente.jpg
85 ms
resumaCarreira.jpg
83 ms
contratasePeloCV.png
85 ms
gpt.js
30 ms
cathoIconFont.svg
87 ms
fp.js
145 ms
cathoFooter.png
72 ms
widgets.js
95 ms
plusone.js
94 ms
pubads_impl_81.js
31 ms
gtm.js
88 ms
st.v3.js
24 ms
ads
108 ms
ads
143 ms
container.html
34 ms
cb=gapi.loaded_0
52 ms
offsite_event.php
135 ms
analytics.js
87 ms
dc.js
107 ms
conversion_async.js
100 ms
spp.pl
177 ms
ld.js
62 ms
fbds.js
119 ms
collect.js
61 ms
zanox.js
250 ms
145 ms
fbevents.js
156 ms
4689
176 ms
spp.pl
165 ms
spp.pl
164 ms
spp.pl
168 ms
activityi;src=5342714;type=invmedia;cat=vervxql4;ord=6294091878179;~oref=http%3A%2F%2Fwww.catho.com.br%2F
117 ms
activityi;src=5342714;type=invmedia;cat=siamn0eb;ord=4041245261696;~oref=http%3A%2F%2Fwww.catho.com.br%2F
116 ms
offsite_event.php
113 ms
14956675583649194502
104 ms
osd.js
60 ms
event
81 ms
track_page_view
111 ms
ecommerce.js
36 ms
15782297733968399376
72 ms
80 ms
__utm.gif
32 ms
83 ms
96 ms
35 ms
collect
37 ms
collect
64 ms
collect
77 ms
collect
30 ms
53 ms
10 ms
9 ms
4689
77 ms
4689
163 ms
4880
163 ms
47 ms
ga-audiences
36 ms
41 ms
ga-audiences
30 ms
30 ms
47E4D1F875BD94FE9968
223 ms
generic
7 ms
dfm-analytics.min.js
12 ms
generic
4 ms
4880
99 ms
cs
98 ms
cm
4 ms
Fvmz6MLb
11 ms
pixel
15 ms
pixel.gif
8 ms
470 ms
ebOneTag.js
89 ms
activity;src=4445911;type=cathop3;cat=Catho000;ord=7131062361877.411
89 ms
85 ms
EventHandler
207 ms
172 ms
142 ms
Serving
23 ms
pixel
14 ms
138 ms
EventHandler
237 ms
r2
4 ms
raptor-2.1.0-brazil.js
64 ms
activityi;src=5370281;type=count0;cat=front0;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=;ord=6838845140300.691
48 ms
273e7fd04e5bf038eb17bee9907b6cfe.css
168 ms
6ab633beab32f0935a558c38841eceac.js
239 ms
f7f57442c95619cb43ce90a912ec377c.js
185 ms
activeview
13 ms
cathoIconFont.svg
84 ms
loadingb2c.gif
136 ms
nr-768.min.js
49 ms
nr-768.min.js
29 ms
11986.gif
1145 ms
dis.aspx
49 ms
24 ms
21014.gif
1135 ms
31288.gif
1137 ms
148946.gif
1136 ms
290672.gif
1138 ms
527782.gif
1140 ms
ffbcf13e6e
69 ms
ffbcf13e6e
129 ms
pix
76 ms
751b9da9-3b19-4ca4-8856-2dbf0425888f
63 ms
spp.pl
47 ms
67 ms
Pug
38 ms
sync
60 ms
rtset
41 ms
85 ms
u.php
63 ms
pixel
41 ms
mapuser
33 ms
match
18 ms
cookiematch.aspx
30 ms
rum
7 ms
cookiematch.aspx
18 ms
tap.php
8 ms
sync
6 ms
u.php
35 ms
cookiematch.aspx
14 ms
set
35 ms
catho.com.br 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
Buttons do not have an accessible name
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
catho.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
Missing source maps for large first-party JavaScript
catho.com.br SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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 Catho.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 Catho.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.
catho.com.br
Open Graph description is not detected on the main page of Catho. 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: