4.4 sec in total
448 ms
3.8 sec
142 ms
Welcome to iaph.es homepage info - get ready to check Iaph best content for Spain right away, or after learning these important things about iaph.es
Sitio web del Instituto Andaluz del Patrimonio Histórico. Descubre a qué se dedica y los servicios que te ofrece.
Visit iaph.esWe analyzed Iaph.es page load time and found that the first response time was 448 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
iaph.es performance score
name
value
score
weighting
Value9.7 s
0/100
10%
Value14.1 s
0/100
25%
Value15.7 s
0/100
10%
Value940 ms
30/100
30%
Value0.003
100/100
15%
Value20.5 s
2/100
10%
448 ms
355 ms
659 ms
354 ms
255 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 96% of them (66 requests) were addressed to the original Iaph.es, 3% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Maps.google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Iaph.es.
Page size can be reduced by 284.4 kB (35%)
812.4 kB
528.0 kB
In fact, the total size of Iaph.es main page is 812.4 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. 20% of websites need less resources to load. Images take 405.5 kB which makes up the majority of the site volume.
Potential reduce by 58.5 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 58.5 kB or 84% of the original size.
Potential reduce by 36 B
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. Iaph images are well optimized though.
Potential reduce by 173.2 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 173.2 kB or 64% of the original size.
Potential reduce by 52.7 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. Iaph.es needs all CSS files to be minified and compressed as it can save up to 52.7 kB or 80% of the original size.
Number of requests can be reduced by 22 (33%)
66
44
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Iaph. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
iaph.es
448 ms
www.iaph.es
355 ms
659 ms
googlemap_key_config.js
354 ms
jquery.fancybox.css
255 ms
estils.css
379 ms
estils_dedit.css
260 ms
coin-slider-styles.css
246 ms
jquery.js
612 ms
coin-slider.js
481 ms
cufon-yui.js
608 ms
univers_condensed.js
634 ms
jquery.fancybox-1.3.4.pack.js
597 ms
jwplayer.js
829 ms
js
52 ms
fondo-top.gif
136 ms
ajax-loader.gif
130 ms
logo_ppal.gif
146 ms
fondoblanco_textoverde.png
164 ms
160208_registro_pica.jpg_1485108330.jpg
381 ms
160114_destacado_88_exposicion_virtual_arguijo.jpg_1485108330.jpg
480 ms
160119_destacado_89_seminario_inmaterial.jpg_1485108330.jpg
507 ms
150430_atlasdelpatrimonioinmaterial.jpg_1485108330.jpg
666 ms
150320_destacado_gphus.jpg_1485108330.jpg
487 ms
160226_cristo_descendimiento_archidona.jpg_1907998425.jpg
405 ms
160223_fiesta_de_la_historia.jpg_1907998425.jpg
556 ms
160223_manto_asuncion_estepa.jpg_1907998425.jpg
588 ms
160222_patrocinadores_colaboradores_seminario.jpg_1907998425.jpg
605 ms
160216_foro_tanmia.jpg_1907998425.jpg
615 ms
160216_reunion_patronato_fundacixn_descubre.jpg_1907998425.jpg
633 ms
160209_fundacion_docomomo_iberico.jpg_1907998425.jpg
682 ms
160209_paisaje_castellar_de_la_frontera_cadiz.jpg_1907998425.jpg
714 ms
1989_g_Sede_Vestxbulo.jpg_1977194444.jpg
734 ms
1996_r_Visitas_didxcticas_x2009x.jpg_1977194444.jpg
745 ms
patrimonio_cultural.jpg_1977194444.jpg
763 ms
conoce_patrimonio.jpg_1977194444.jpg
793 ms
Icono_Canal_Arqueologxa_Subacuxtica.jpg_1977194444.jpg
810 ms
2003_c_Laboratorio_de_Biologxa.jpg_1977194444.jpg
844 ms
Apolo.jpg_1977194444.jpg
862 ms
1996_x_Puertas_Abiertas_x2009x.jpg_1977194444.jpg
875 ms
Banner_guia_estancias_cursos.jpg
902 ms
banner_enlinea.jpg
920 ms
logo_rea.png
935 ms
publicaciones05.jpg
972 ms
banner_didactica.jpg
997 ms
blog.jpg
1002 ms
ico_foot_face.gif
1029 ms
logo_comp_youtube.gif
1047 ms
twitter.gif
1062 ms
gooicono.jpg
1101 ms
24px-Wikipedia-logo_copia.png
1123 ms
ga.js
30 ms
__utm.gif
12 ms
wikanda.png
1006 ms
logo_comp_rss.gif
1026 ms
logo_linkedin_2.png
1032 ms
creative.jpg
1029 ms
w3_css.png
848 ms
w3_wai.png
852 ms
w3_html.png
782 ms
borde01.png
796 ms
fondo_enlaz02.gif
793 ms
ico_pag_anterior1.gif
760 ms
ico_pag_siguiente1.gif
763 ms
fondo-agenda.gif
777 ms
opcionesmenu.png
773 ms
bullet03.png
773 ms
barra-slide.png
760 ms
print.css
131 ms
iaph.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
[aria-hidden="true"] elements contain focusable descendents
iaph.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
iaph.es 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
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
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iaph.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 Iaph.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.
iaph.es
Open Graph description is not detected on the main page of Iaph. 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: