3.9 sec in total
234 ms
3.4 sec
319 ms
Click here to check amazing Faesc content. Otherwise, check out these important facts you probably never knew about faesc.com
Visit faesc.comWe analyzed Faesc.com page load time and found that the first response time was 234 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
faesc.com performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value4.3 s
41/100
25%
Value3.5 s
88/100
10%
Value250 ms
85/100
30%
Value0.069
96/100
15%
Value4.4 s
83/100
10%
234 ms
857 ms
41 ms
631 ms
105 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Faesc.com, 86% (77 requests) were made to Faesc.edu.br and 8% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (912 ms) relates to the external source Faesc.edu.br.
Page size can be reduced by 1.5 MB (25%)
5.9 MB
4.4 MB
In fact, the total size of Faesc.com main page is 5.9 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. Images take 4.9 MB which makes up the majority of the site volume.
Potential reduce by 50.9 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 50.9 kB or 82% of the original size.
Potential reduce by 702.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. Obviously, Faesc needs image optimization as it can save up to 702.1 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 315.5 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 315.5 kB or 74% of the original size.
Potential reduce by 428.5 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. Faesc.com needs all CSS files to be minified and compressed as it can save up to 428.5 kB or 83% of the original size.
Number of requests can be reduced by 53 (72%)
74
21
The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Faesc. 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 21 to 1 for CSS and as a result speed up the page load time.
faesc.com
234 ms
www.faesc.edu.br
857 ms
faesc
41 ms
631 ms
wp-emoji-release.min.js
105 ms
animate.css
143 ms
frontend.css
76 ms
font-awesome.min.css
16 ms
css
23 ms
frontend.css
108 ms
styles.css
73 ms
style.css
115 ms
ecwd_popup.css
114 ms
font-awesome.css
147 ms
style.css
205 ms
dashicons.min.css
214 ms
main.min.css
157 ms
css
40 ms
font-awesome.min.css
151 ms
jquery.bxslider.css
177 ms
nivo-lightbox.css
183 ms
animate.css
218 ms
style.css
264 ms
responsive.css
215 ms
font-awesome.css
257 ms
jquery.js
309 ms
jquery-migrate.min.js
243 ms
jquery.cookie.js
256 ms
frontend.js
255 ms
gmap3.js
309 ms
ecwd_popup.js
254 ms
core.min.js
255 ms
widget.min.js
254 ms
mouse.min.js
260 ms
draggable.min.js
309 ms
masonry.min.js
353 ms
scripts.js
308 ms
frontend.js
309 ms
jquery.form.min.js
310 ms
scripts.js
310 ms
jquery.masonry.min.js
366 ms
rsvp.js
366 ms
wow.js
366 ms
SmoothScroll.js
341 ms
parallax.js
341 ms
jquery.scrollTo.min.js
319 ms
jquery.localScroll.min.js
316 ms
jquery.nav.js
314 ms
jquery.bxslider.min.js
335 ms
jquery.easing.min.js
309 ms
jquery.fitvids.js
304 ms
jquery.actual.min.js
309 ms
nivo-lightbox.min.js
306 ms
skip-link-focus-fix.js
287 ms
custom.js
280 ms
hoverIntent.min.js
254 ms
maxmegamenu.js
252 ms
wp-embed.min.js
278 ms
bg.png
157 ms
topo_faesc2.png
264 ms
Cartaz-FAESCok-480x300.png
259 ms
IMG_5627-480x300.jpg
197 ms
foto07-480x300.jpg
195 ms
mapa_FAESC2.png
425 ms
marca_FAESC.fw_.png
299 ms
aula_magna-enf.jpg
264 ms
overlay4.png
224 ms
down-arrow.png
263 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
10 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
9 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
41 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
40 ms
6nvU963vW96zvuZHXyGvkNfLa8try2vLa8try2vLa8try2vLaPbzi90vRj6IfRT+KfhS9KHpR9KLoRdGLohdFL4peFL0oelH0ouhF0YuiF0Uvil4UvSh6UfSi6EXRi6IXRS+KXhS9KHpR9KHoQ9GHog9FH4o+FD0oelD0oOToN3TgiAFDRg4b9C8VmLmgAAAAAVWwJZkAAA==
6 ms
Cartaz-FAESCok.png
406 ms
IMG_5627.jpg
315 ms
foto07.jpg
310 ms
AsfVxh0LishHwqaXKl94esUNZKBtHD0L7honx3zUdXJo.jpg
360 ms
912 ms
DSC_8994.jpg
712 ms
yVHpdQrmTj9Kax1tmFSx2qCWcynf_cDxXwCLxiixG1c.ttf
11 ms
f8OBjBbevvywgbyJOxlO7Q.ttf
11 ms
AwBqWF2kjhlybWamaKMPcaCWcynf_cDxXwCLxiixG1c.ttf
37 ms
fontawesome-webfont.woff
519 ms
fontawesome-webfont.woff
518 ms
fontawesome-webfont.woff
519 ms
fontawesome-webfont.woff
38 ms
calendar.css
387 ms
bx_loader.gif
42 ms
controls.png
42 ms
ajax-loader.gif
41 ms
faesc.com 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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
faesc.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
faesc.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
N/A
PT
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Faesc.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Portuguese. Our system also found out that Faesc.com 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.
faesc.com
Open Graph description is not detected on the main page of Faesc. 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: