3.2 sec in total
687 ms
1.8 sec
786 ms
Welcome to saee.com.br homepage info - get ready to check SAEE best content for Brazil right away, or after learning these important things about saee.com.br
Desde 2009, aproximando currículos de vagas, ingressando pessoas no mercado de trabalho, por meio do recrutamento, contribuindo para a construção de carreira e colaborando para o desenvolvimento na vi...
Visit saee.com.brWe analyzed Saee.com.br page load time and found that the first response time was 687 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
saee.com.br performance score
name
value
score
weighting
Value3.4 s
36/100
10%
Value11.7 s
0/100
25%
Value7.8 s
24/100
10%
Value570 ms
52/100
30%
Value0
100/100
15%
Value13.3 s
12/100
10%
687 ms
47 ms
57 ms
57 ms
55 ms
Our browser made a total of 94 requests to load all elements on the main page. We found that 57% of them (54 requests) were addressed to the original Saee.com.br, 14% (13 requests) were made to Fonts.gstatic.com and 11% (10 requests) were made to Sitebot.builderall.com. The less responsive or slowest element that took the longest time to load (687 ms) belongs to the original domain Saee.com.br.
Page size can be reduced by 847.5 kB (28%)
3.1 MB
2.2 MB
In fact, the total size of Saee.com.br main page is 3.1 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 1.8 MB which makes up the majority of the site volume.
Potential reduce by 52.2 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 25.0 kB, which is 42% 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 52.2 kB or 87% of the original size.
Potential reduce by 66.3 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. SAEE images are well optimized though.
Potential reduce by 496.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 496.1 kB or 57% of the original size.
Potential reduce by 233.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. Saee.com.br needs all CSS files to be minified and compressed as it can save up to 233.0 kB or 63% of the original size.
Number of requests can be reduced by 57 (75%)
76
19
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of SAEE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 21 to 1 for CSS and as a result speed up the page load time.
saee.com.br
687 ms
bootstrap.min.css
47 ms
owl.carousel.min.css
57 ms
flaticon.css
57 ms
price_rangs.css
55 ms
slicknav.css
60 ms
animate.min.css
66 ms
magnific-popup.css
69 ms
fontawesome-all.min.css
77 ms
themify-icons.css
81 ms
slick.css
75 ms
nice-select.css
79 ms
style.css
114 ms
jquery-3.7.1.min.js
35 ms
scripts.js
91 ms
js
79 ms
bootstrap-select.min.css
300 ms
whatsapp-button.css
69 ms
cookieconsent.min.css
31 ms
cookieconsent.min.js
48 ms
modernizr-3.5.0.min.js
94 ms
jquery-1.12.4.min.js
120 ms
popper.min.js
99 ms
bootstrap.min.js
125 ms
jquery.slicknav.min.js
118 ms
owl.carousel.min.js
139 ms
slick.min.js
124 ms
price_rangs.js
140 ms
wow.min.js
134 ms
animated.headline.js
141 ms
jquery.magnific-popup.js
202 ms
jquery.scrollUp.min.js
202 ms
jquery.nice-select.min.js
203 ms
jquery.sticky.js
202 ms
contact.js
441 ms
jquery.form.js
204 ms
jquery.validate.min.js
202 ms
mail-script.js
203 ms
jquery.ajaxchimp.min.js
204 ms
plugins.js
204 ms
main.js
204 ms
bootstrap-select.min.js
32 ms
css
35 ms
gtm.js
47 ms
logo.png
42 ms
logos.png
44 ms
job-list.png
67 ms
comment_1.png
67 ms
comment_2.png
67 ms
comment_3.png
68 ms
whatsapp-icon.svg
99 ms
support-img.jpg
102 ms
home-blog1.jpg
103 ms
home-blog2.jpg
103 ms
form.png
99 ms
logo2_footer.png
100 ms
7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e0.ttf
230 ms
7Aulp_0qiz-aVz7u3PJLcUMYOFn8kEk30e0.ttf
247 ms
7Aulp_0qiz-aVz7u3PJLcUMYOFmQkEk30e0.ttf
228 ms
7Aulp_0qiz-aVz7u3PJLcUMYOFkQl0k30e0.ttf
229 ms
7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k30e0.ttf
248 ms
7Aulp_0qiz-aVz7u3PJLcUMYOFlOl0k30e0.ttf
399 ms
7Aulp_0qiz-aVz7u3PJLcUMYOFlnl0k30e0.ttf
249 ms
7cHqv4kjgoGqM7E3_-gs51op.ttf
250 ms
7cHpv4kjgoGqM7E_DMs8.ttf
248 ms
7cHqv4kjgoGqM7E3p-ks51op.ttf
249 ms
7cHqv4kjgoGqM7E30-8s51op.ttf
249 ms
7cHqv4kjgoGqM7E3t-4s51op.ttf
249 ms
7cHqv4kjgoGqM7E3j-ws51op.ttf
249 ms
Flaticon.svg
198 ms
Flaticon.woff
198 ms
fa-solid-900.woff
197 ms
fa-regular-400.woff
187 ms
sitebot.php
328 ms
h1_hero.jpg
97 ms
cv_bg.jpg
97 ms
how-applybg.png
65 ms
fa-brands-400.woff
94 ms
icon
18 ms
css
27 ms
materialize.css
104 ms
intlTelInput.css
113 ms
style.css
160 ms
jquery.min.js
21 ms
popper.min.js
11 ms
angular.min.js
26 ms
angular-animate.js
61 ms
intlTelInput-jquery.js
133 ms
utils.js
214 ms
jquery.mask.js
111 ms
materialize.min.js
154 ms
angular-materialize.min.js
13 ms
app.js
129 ms
sitebot.js
138 ms
saee.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
Image elements do not have [alt] attributes
Links do not have a discernible name
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
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
saee.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
saee.com.br 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
Tap targets are not sized appropriately
![]()
PT
![]()
ZX
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Saee.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 language. Our system also found out that Saee.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.
saee.com.br
Open Graph description is not detected on the main page of SAEE. 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: