3.9 sec in total
600 ms
3.1 sec
199 ms
Visit anaygar.es now to see the best up-to-date Anay Gar content and also check out these interesting facts you probably never knew about anaygar.es
En Anaygar estamos especializados en la fabricación de Carpinteria aluminio Zaragoza. ¡Entra, conocenos y pregunta cualquier duda que te surja!
Visit anaygar.esWe analyzed Anaygar.es page load time and found that the first response time was 600 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.
anaygar.es performance score
name
value
score
weighting
Value4.3 s
18/100
10%
Value4.8 s
30/100
25%
Value6.8 s
34/100
10%
Value140 ms
96/100
30%
Value0.267
46/100
15%
Value7.3 s
50/100
10%
600 ms
84 ms
155 ms
158 ms
161 ms
Our browser made a total of 49 requests to load all elements on the main page. We found that 84% of them (41 requests) were addressed to the original Anaygar.es, 8% (4 requests) were made to Maps.googleapis.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (613 ms) belongs to the original domain Anaygar.es.
Page size can be reduced by 281.5 kB (17%)
1.7 MB
1.4 MB
In fact, the total size of Anaygar.es main page is 1.7 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. 35% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 42.6 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 42.6 kB or 78% of the original size.
Potential reduce by 20.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. Anay Gar images are well optimized though.
Potential reduce by 210.8 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 210.8 kB or 51% of the original size.
Potential reduce by 8.1 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. Anaygar.es needs all CSS files to be minified and compressed as it can save up to 8.1 kB or 39% of the original size.
Number of requests can be reduced by 28 (60%)
47
19
The browser has sent 47 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Anay Gar. 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 7 to 1 for CSS and as a result speed up the page load time.
www.anaygar.es
600 ms
wp-emoji-release.min.js
84 ms
style.css
155 ms
nivo-slider.css
158 ms
noscript.css
161 ms
prettyPhoto.css
164 ms
style.css
167 ms
styles.css
168 ms
jquery.fancybox-1.3.8.min.css
230 ms
jquery-1.6.4.min.js
312 ms
cufon-yui.js
324 ms
Akzidenz-Grotesk_Next_Regular_400-Akzidenz-Grotesk_Next_Bold_700.font.js
327 ms
Brush_Script_Std_italic_500.font.js
454 ms
jqueryslidemenu.js
250 ms
jquery.nivo.slider.js
305 ms
jquery.easing.1.3.js
333 ms
quicksand.js
382 ms
quicksand_config.js
388 ms
jquery.prettyPhoto.js
397 ms
ts-portfolio-fade.js
414 ms
jquery.form.min.js
415 ms
scripts.js
495 ms
wp-embed.min.js
497 ms
jquery.fancybox-1.3.8.min.js
508 ms
jquery.easing.min.js
510 ms
jquery.mousewheel.min.js
512 ms
anaygar_logo.png
163 ms
embed
210 ms
slider1.jpg
518 ms
slider2.jpg
513 ms
slider3.jpg
613 ms
slider4.jpg
537 ms
anaygar-contacto.png
125 ms
menu-separator.gif
125 ms
1013946_540848092628736_884025221_n-300x225.jpg
125 ms
twitter.png
129 ms
vimeo.png
126 ms
rss.png
154 ms
google.png
207 ms
analytics.js
78 ms
down.gif
80 ms
collect
16 ms
js
72 ms
js
68 ms
search.js
6 ms
geometry.js
12 ms
main.js
16 ms
bg-text-slide.png
84 ms
nav-slide.png
85 ms
anaygar.es 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
button, link, and menuitem elements do not have accessible names.
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
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Some elements have a [tabindex] value greater than 0
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.
anaygar.es 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
General
Impact
Issue
Detected JavaScript libraries
anaygar.es SEO score
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Anaygar.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 Anaygar.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.
anaygar.es
Open Graph data is detected on the main page of Anay Gar. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: