3.6 sec in total
391 ms
2.8 sec
439 ms
Click here to check amazing ENA content for Portugal. Otherwise, check out these important facts you probably never knew about ena.pt
Desde 100€ em várias localizações: Gaia, Matosinhos, Penafiel, Lisboa, Aveiro. Curso de Formação de Formadores em B-learning e em versão mobile certificado pelo IEFP e com a duração de 90 horas.
Visit ena.ptWe analyzed Ena.pt page load time and found that the first response time was 391 ms and then it took 3.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
ena.pt performance score
name
value
score
weighting
Value2.5 s
69/100
10%
Value12.7 s
0/100
25%
Value6.2 s
43/100
10%
Value700 ms
42/100
30%
Value1.166
1/100
15%
Value15.6 s
6/100
10%
391 ms
448 ms
122 ms
39 ms
97 ms
Our browser made a total of 53 requests to load all elements on the main page. We found that 58% of them (31 requests) were addressed to the original Ena.pt, 25% (13 requests) were made to Embed.tawk.to and 8% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Ena.pt.
Page size can be reduced by 168.8 kB (6%)
2.9 MB
2.7 MB
In fact, the total size of Ena.pt main page is 2.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. 45% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.
Potential reduce by 46.4 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.3 kB, which is 20% 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 46.4 kB or 82% of the original size.
Potential reduce by 99.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. ENA images are well optimized though.
Potential reduce by 23.3 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 23.3 kB or 11% of the original size.
Potential reduce by 34 B
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. Ena.pt has all CSS files already compressed.
Number of requests can be reduced by 20 (43%)
47
27
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ENA. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
ena.pt
391 ms
ena.pt
448 ms
app.min.css
122 ms
css
39 ms
js
97 ms
app.min.js
336 ms
flickity.min.css
305 ms
flickity.min.js
312 ms
sweetalert2.min.css
37 ms
sweetalert2.min.js
51 ms
gtm.js
48 ms
facebook-menu-white.svg
124 ms
instagram-menu-white.svg
128 ms
linkedin-menu-white.svg
126 ms
ena_logo.svg
124 ms
Cheque_Formacao_570x270.png
303 ms
horario.svg
242 ms
telefone.svg
240 ms
smartphone.svg
242 ms
local.svg
302 ms
email.svg
306 ms
dgert.jpg
333 ms
iefp.jpg
333 ms
act.jpg
335 ms
easypay_visa.png
488 ms
ccp_1180.jpg
1144 ms
vantagem.jpg
857 ms
e_formador_1180.jpg
1311 ms
pandemia_1180.jpg
1272 ms
ccp.jpg
697 ms
d369fac2409350693ac1cf87ad60ca28.jpg
757 ms
2cbea813cba37fb9cb7a378e7370726d.jpg
1260 ms
d7575099c0db090b27ed6ac5640a5640.jpg
945 ms
36c2f119848f8470c0e42f28722f8905.jpg
1045 ms
487ef234f2c30787573bef3ea0cd115a.jpg
1132 ms
9f8b6c4310de2539821d258e068810ee.jpg
1231 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
52 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
52 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
65 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
69 ms
default
207 ms
twk-arr-find-polyfill.js
190 ms
twk-object-values-polyfill.js
185 ms
twk-event-polyfill.js
72 ms
twk-entries-polyfill.js
63 ms
twk-iterator-polyfill.js
189 ms
twk-promise-polyfill.js
61 ms
twk-main.js
118 ms
twk-vendor.js
169 ms
twk-chunk-vendors.js
208 ms
twk-chunk-common.js
249 ms
twk-runtime.js
226 ms
twk-app.js
234 ms
ena.pt 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-hidden="true"] elements contain focusable descendents
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
ena.pt 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
Browser errors were logged to the console
Page has valid source maps
ena.pt SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ena.pt 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 Ena.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.
ena.pt
Open Graph data is detected on the main page of ENA. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: