10.4 sec in total
2.5 sec
7.7 sec
208 ms
Click here to check amazing Fenster content for Spain. Otherwise, check out these important facts you probably never knew about fenster.es
FENSTER se dedica a la fabricación e instalación de ventanas de aluminio y pvc, acristalamientos, muros cortina, revestimientos de fachada y complementos
Visit fenster.esWe analyzed Fenster.es page load time and found that the first response time was 2.5 sec and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
fenster.es performance score
name
value
score
weighting
Value3.6 s
32/100
10%
Value7.6 s
4/100
25%
Value12.7 s
3/100
10%
Value940 ms
30/100
30%
Value0.072
96/100
15%
Value11.3 s
20/100
10%
2546 ms
112 ms
24 ms
36 ms
216 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 93% of them (63 requests) were addressed to the original Fenster.es, 3% (2 requests) were made to Fonts.googleapis.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Fenster.es.
Page size can be reduced by 374.9 kB (25%)
1.5 MB
1.1 MB
In fact, the total size of Fenster.es main page is 1.5 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 1.1 MB which makes up the majority of the site volume.
Potential reduce by 31.3 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 31.3 kB or 77% of the original size.
Potential reduce by 86.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. Fenster images are well optimized though.
Potential reduce by 169.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 169.1 kB or 65% of the original size.
Potential reduce by 88.3 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. Fenster.es needs all CSS files to be minified and compressed as it can save up to 88.3 kB or 83% of the original size.
Number of requests can be reduced by 38 (59%)
64
26
The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fenster. 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 13 to 1 for CSS and as a result speed up the page load time.
www.fenster.es
2546 ms
language-selector.css
112 ms
css
24 ms
css
36 ms
style.css
216 ms
estilos.css
237 ms
styles.css
239 ms
shortcodes.css
240 ms
shortcodes_responsive.css
238 ms
nivo-slider.css
245 ms
easy-nivo-slider.css
323 ms
jquery.fancybox-1.3.4.css
320 ms
page_templates.css
324 ms
jquery.js
444 ms
jquery-migrate.min.js
330 ms
principal.js
336 ms
jquery.nivo.slider.js
428 ms
flexslider.css
427 ms
jquery.form.min.js
429 ms
scripts.js
438 ms
superfish.js
487 ms
jquery.flexslider-min.js
535 ms
jquery.fitvids.js
535 ms
custom.js
537 ms
jquery.easing-1.3.pack.js
549 ms
jquery.fancybox-1.3.4.pack.js
551 ms
et-ptemplates-frontend.js
556 ms
sitepress.js
638 ms
et_shortcodes_frontend.js
640 ms
wp-emoji-release.min.js
449 ms
nav-arrow-down.png
212 ms
es.png
213 ms
fr.png
212 ms
en.png
282 ms
ca.png
282 ms
facebook_Fenster.png
285 ms
linkedin_Fenster.png
302 ms
you_tube_Fenster.png
307 ms
telefono-fenster-31.png
314 ms
logo.png
388 ms
fondo.png
387 ms
search_btn.png
391 ms
foto231.jpg
1153 ms
foto36b1.jpg
1056 ms
foto37.jpg
1077 ms
foto211.jpg
1213 ms
main_sprite.png
598 ms
ayudas-pub1.jpg
599 ms
q-railing-esp1.jpg
809 ms
veka1.png
918 ms
logo-technal.jpg
917 ms
cortizo.png
1127 ms
shuco.png
1025 ms
logo-jansen.jpg
1133 ms
logo_climalit_4.jpg
1162 ms
ga.js
6 ms
logo_aislaglas.jpg
1173 ms
logo_aenor2.png
1218 ms
__utm.gif
14 ms
collect
53 ms
logo_cekal.png
1179 ms
logo_qualanod.png
1197 ms
logo_qualicoat.png
1206 ms
logo_ce.png
1221 ms
logo_rea3.jpg
1237 ms
aplus.png
1360 ms
bg_control_nav.png
1255 ms
bg_direction_nav.png
1242 ms
fenster.es 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.
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
Image elements do not have [alt] attributes
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.
fenster.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
fenster.es 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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fenster.es 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 Fenster.es 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.
fenster.es
Open Graph data is detected on the main page of Fenster. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: