3.1 sec in total
242 ms
2.5 sec
313 ms
Click here to check amazing Portore content. Otherwise, check out these important facts you probably never knew about portore.eu
Fabricante de Puertas de garaje, especialista en puertas de garaje, persianas y puertas automáticas. Fabricación, venta, instalación, mantenimiento y reparación
Visit portore.euWe analyzed Portore.eu page load time and found that the first response time was 242 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
portore.eu performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value8.9 s
1/100
25%
Value19.8 s
0/100
10%
Value21,250 ms
0/100
30%
Value0.191
64/100
15%
Value33.5 s
0/100
10%
242 ms
843 ms
274 ms
368 ms
484 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Portore.eu, 81% (42 requests) were made to Portore.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (915 ms) relates to the external source Portore.com.
Page size can be reduced by 411.4 kB (42%)
987.7 kB
576.2 kB
In fact, the total size of Portore.eu main page is 987.7 kB. 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 531.9 kB which makes up the majority of the site volume.
Potential reduce by 33.0 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 33.0 kB or 78% of the original size.
Potential reduce by 18.8 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. Portore images are well optimized though.
Potential reduce by 359.7 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 359.7 kB or 68% of the original size.
Number of requests can be reduced by 28 (58%)
48
20
The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Portore. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
portore.eu
242 ms
portore.com
843 ms
gzip.php
274 ms
gzip.php
368 ms
css
484 ms
css
512 ms
css
510 ms
jquery.js
36 ms
gzip.php
393 ms
gzip.php
529 ms
gzip.php
575 ms
gzip.php
607 ms
gzip.php
684 ms
gzip.php
731 ms
gzip.php
798 ms
chosen.min.js
622 ms
js
892 ms
fileuploader.min.js
715 ms
gzip.php
838 ms
css
27 ms
gzip.php
915 ms
search.js
832 ms
lightbox.js
98 ms
mediaelement-and-player.js
171 ms
spotlight.js
255 ms
ga.js
69 ms
desert_img.jpg
430 ms
social_icons.png
110 ms
Logo-PortoreWeb2.png
396 ms
button_more_white-PQ.png
108 ms
icon_menu_home.png
109 ms
icon_menu_features.png
110 ms
icon_menu_icons.png
392 ms
icon_menu_zoo.png
392 ms
PortoreEmpresa_02.jpg
424 ms
ahorro.jpg
423 ms
acabados.png
427 ms
colores.png
424 ms
anodizado.png
424 ms
madera.png
426 ms
icon_gallery.png
426 ms
icon_contact.png
426 ms
icon_tool.png
469 ms
YDAoLskQQ5MOAgvHUQCcLbvy90DtE_Pg_qiF9bHvTzw.ttf
40 ms
We_iSDqttE3etzfdfhuPRX4NhRhUVU1NOvrEWRXSCoI.ttf
40 ms
__utm.gif
21 ms
bg.png
386 ms
all.js
16 ms
OpenSans-Light-webfont.woff
397 ms
slideshow.js
148 ms
widgets.js
108 ms
plusone.js
105 ms
portore.eu 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-*] attributes do not match their roles
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
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
portore.eu 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
portore.eu SEO score
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Portore.eu can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Portore.eu 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.
portore.eu
Open Graph description is not detected on the main page of Portore. 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: