17.7 sec in total
4 sec
12.5 sec
1.1 sec
Click here to check amazing Essl content. Otherwise, check out these important facts you probably never knew about essl.pt
Portal do AESL
Visit essl.ptWe analyzed Essl.pt page load time and found that the first response time was 4 sec and then it took 13.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
essl.pt performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value20.9 s
0/100
25%
Value30.2 s
0/100
10%
Value44,460 ms
0/100
30%
Value0.034
100/100
15%
Value116.3 s
0/100
10%
4042 ms
256 ms
252 ms
256 ms
617 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 87% of them (81 requests) were addressed to the original Essl.pt, 3% (3 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.3 sec) belongs to the original domain Essl.pt.
Page size can be reduced by 2.3 MB (19%)
12.3 MB
10.0 MB
In fact, the total size of Essl.pt main page is 12.3 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. 55% of websites need less resources to load. Images take 10.8 MB which makes up the majority of the site volume.
Potential reduce by 78.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 11.9 kB, which is 13% 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 78.2 kB or 85% of the original size.
Potential reduce by 1.1 MB
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. Essl images are well optimized though.
Potential reduce by 351.4 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 351.4 kB or 67% of the original size.
Potential reduce by 813.6 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. Essl.pt needs all CSS files to be minified and compressed as it can save up to 813.6 kB or 85% of the original size.
Number of requests can be reduced by 44 (50%)
88
44
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Essl. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
essl.pt
4042 ms
style.css
256 ms
general.css
252 ms
system.css
256 ms
bootstrap.min.css
617 ms
template-green.css
605 ms
pattern.css
523 ms
jquery.mmenu.all.css
662 ms
your_css.css
502 ms
font-awesome.css
707 ms
responsive.css
865 ms
css
25 ms
bootstrap.css
1119 ms
glyphicon.css
853 ms
shortcodes.css
1129 ms
template.css
915 ms
modstyle.css
960 ms
bootstrap.css
1568 ms
bootstrap-responsive.css
1230 ms
mod_sj_carousel.css
1157 ms
style.css
1211 ms
finder.css
1363 ms
jquery.min.js
1709 ms
jquery-noconflict.js
1405 ms
keepmenu.js
1460 ms
scrollReveal.js
1479 ms
yt-script.js
1611 ms
jquery.mmenu.min.all.js
1756 ms
touchswipe.min.js
1707 ms
jquery.easing.1.3.js
1733 ms
jquery.megamenu.js
1815 ms
gooeymenu.js
1866 ms
bootstrap.min.js
2070 ms
touchswipe.min.js
1960 ms
jquery.prettyPhoto.js
2095 ms
prettify.js
2119 ms
shortcodes.js
2052 ms
calnav.js
1883 ms
system.css
1967 ms
jquery-noconflict.js
2066 ms
jquery-migrate.min.js
1995 ms
bootstrap.min.js
1972 ms
ga.js
21 ms
logo1.png
139 ms
a2208b4bcbe2684bd9df0c8ea97ebb7b.png
1784 ms
813299a101ce855c15c1bde7db7fbc87.png
1594 ms
866bdd9fda125bee31341ca98bacc258.png
1873 ms
7130cc8571bdd5008f6c1762c352e02d.png
1876 ms
20fadda847a42e3654e4f9e26e843160.png
1987 ms
a10a60f205399cf89e50f3b780c715ef.png
2050 ms
e210d7454d45c41cfb2f1cfe02464929.png
3220 ms
1fd79e144f802278d59c8cf7c923a1b7.png
3411 ms
2bca81c8d3f1d7aaf592a740a3a9a274.png
3656 ms
eb7ca9623fe728756fcc6d71953ec010.png
3615 ms
c4c9433dce4b14eeedf80bdbf8537753.png
2696 ms
d265c5abd13df75d4276dd950c65571b.png
2622 ms
6f0a00928c777318dc81dc6678c1df16.png
3332 ms
e9697fdbd819bb7c9bebf0af47ccc9e9.png
3407 ms
f525597ef30cc44b98732d3fe6f99103.png
3699 ms
8da40bd15d599af96b31c51c36385652.jpeg
3926 ms
329cfcbf96fd009767437df863b8eb37.png
3981 ms
5b90c575664a1fb5826cbcb8dd281749.png
4121 ms
fd8adf00736d9bfc5acc59db663dda03.png
4553 ms
cb6b696918858320af45dad1db5e6adf.jpeg
4284 ms
b41ebefe5dc520fc107a89236fdcd45c.jpeg
4414 ms
abcfb833110ae838c93b628ba39e9bd5.png
4753 ms
601525771ebc2d7a59206fb353b8fbe0.png
4804 ms
7573e5d980d9547506bcf81a15d34d95.png
4946 ms
mini_arrowleft.gif
4538 ms
mini_arrowright.gif
4667 ms
eadh.png
5711 ms
eco_escolas.png
5032 ms
deco_banner_640x480.png
5243 ms
130268_ZkZWS.png
5805 ms
escolainglesa.png
6327 ms
__utm.gif
14 ms
fontawesome-webfont.woff
5370 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
7 ms
icon_date.png
5209 ms
icon_hits.png
5423 ms
arrow_left.png
5458 ms
arrow_right.png
5521 ms
0VoOualbDKA
47 ms
waADcna7Ig0
50 ms
www-embed-player-vflfNyN_r.css
54 ms
www-embed-player.js
80 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
44 ms
ad_status.js
54 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
32 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
35 ms
icon_cong2.png
4162 ms
icon_hits2.png
4003 ms
glyphicons-halflings.png
4065 ms
essl.pt accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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>).
essl.pt 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
Browser errors were logged to the console
essl.pt 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
Image elements do not have [alt] attributes
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 Essl.pt 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 Essl.pt 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.
essl.pt
Open Graph description is not detected on the main page of Essl. 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: