6.7 sec in total
238 ms
3.7 sec
2.8 sec
Welcome to homeespana.com homepage info - get ready to check Home Espana best content for Netherlands right away, or after learning these important things about homeespana.com
HomeEspaña - Spanish Estate Agent. Buy or Sell Spanish Property. Costa Blanca, Valencia, Alicante, Murcia. 5 offices. Over 2,000 properties for sale in Spain.
Visit homeespana.comWe analyzed Homeespana.com page load time and found that the first response time was 238 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
homeespana.com performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value29.0 s
0/100
25%
Value31.7 s
0/100
10%
Value33,450 ms
0/100
30%
Value0
100/100
15%
Value49.6 s
0/100
10%
238 ms
62 ms
140 ms
129 ms
108 ms
Our browser made a total of 123 requests to load all elements on the main page. We found that 85% of them (104 requests) were addressed to the original Homeespana.com, 3% (4 requests) were made to Unpkg.com and 2% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Admin.homeespana.co.uk.
Page size can be reduced by 476.6 kB (23%)
2.1 MB
1.6 MB
In fact, the total size of Homeespana.com main page is 2.1 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 458.9 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 458.9 kB or 87% of the original size.
Potential reduce by 8.6 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. Home Espana images are well optimized though.
Potential reduce by 5.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. This website has mostly compressed JavaScripts.
Potential reduce by 3.9 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. Homeespana.com has all CSS files already compressed.
Number of requests can be reduced by 81 (79%)
102
21
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Home Espana. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 57 to 1 for JavaScripts and from 26 to 1 for CSS and as a result speed up the page load time.
www.homeespana.com
238 ms
js
62 ms
wp-emoji-release.min.js
140 ms
style.min.css
129 ms
external-images.css
108 ms
main.min.css
148 ms
all.min.css
240 ms
vendors.css
244 ms
leaflet.css
62 ms
frontend-styles.min.css
250 ms
custom-frontend-lite.min.css
440 ms
custom-pro-frontend-lite.min.css
247 ms
frontend.css
245 ms
elementor-styles.min.css
267 ms
v4-shims.min.css
289 ms
jquery-ui.css
284 ms
flatpickr.min.css
298 ms
ecs-style.css
303 ms
style.css
343 ms
custom.css
338 ms
style.css
383 ms
child-custom.css
390 ms
js
146 ms
analytics.js
142 ms
frontend-gtag.min.js
367 ms
jquery.min.js
419 ms
jquery-migrate.min.js
435 ms
external-images.js
443 ms
v4-shims.min.js
449 ms
ecs_ajax_pagination.js
462 ms
ecs.js
499 ms
custom-pro-widget-nav-menu.min.css
490 ms
custom-widget-icon-list.min.css
550 ms
custom-pro-widget-call-to-action.min.css
564 ms
widget-carousel.min.css
560 ms
owl.carousel.css
607 ms
custom-widget-icon-box.min.css
608 ms
animations.min.css
607 ms
jquery.form.min.js
1108 ms
jquery.validate.min.js
894 ms
leaflet.js
110 ms
leaflet.css
175 ms
ere-frontend.js
890 ms
progressbar.min.js
858 ms
inspiry-search-form.js
855 ms
leaflet.js
130 ms
custom.js
788 ms
linkid.js
36 ms
ajax-search.js
710 ms
inspiry-login.js
700 ms
lightbox-open-street-map.js
702 ms
vendors.js
701 ms
locations.js
969 ms
collect
38 ms
common-custom.js
930 ms
cfos.js
862 ms
core.min.js
926 ms
mouse.min.js
922 ms
collect
27 ms
slider.min.js
1161 ms
ga-audiences
31 ms
jquery.ui.touch-punch.min.js
1124 ms
flatpickr.min.js
1120 ms
child-custom.js
1086 ms
jquery.smartmenus.min.js
1073 ms
make-column-clickable.js
1066 ms
imagesloaded.min.js
1209 ms
owl.carousel.min.js
1236 ms
webpack.runtime.min.js
1241 ms
frontend-modules.min.js
1227 ms
waypoints.min.js
1227 ms
frontend.min.js
1215 ms
ecspro.js
1197 ms
gtm.js
68 ms
8327559.jpg
1157 ms
8327645.jpg
1516 ms
8326927.jpg
1159 ms
webpack-pro.runtime.min.js
1139 ms
regenerator-runtime.min.js
1134 ms
wp-polyfill.min.js
1150 ms
hooks.min.js
1148 ms
i18n.min.js
1102 ms
frontend.min.js
1439 ms
elements-handlers.min.js
1150 ms
frontend.js
1152 ms
underscore.min.js
1153 ms
wp-util.min.js
1151 ms
frontend.min.js
1151 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
1157 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
1154 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
1154 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf
1163 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf
1159 ms
bat.js
696 ms
fbevents.js
509 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
1131 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
889 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf
890 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf
891 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9WXh0ow.ttf
885 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9WXh0ow.ttf
888 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq_p9WXh0ow.ttf
712 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR9WXh0ow.ttf
645 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R8WXh0ow.ttf
673 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq3p6WXh0ow.ttf
646 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6WXh0ow.ttf
670 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR6WXh0ow.ttf
666 ms
JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqw16WXh0ow.ttf
665 ms
HomeEspana_Logo.svg
436 ms
nav-menu.svg
442 ms
HomeEspana_Logo-1.png
432 ms
HomeEspana_Logo_Blue.svg
437 ms
Selling-your-Spanish-Property-1.jpg
439 ms
New-Build-Property-for-sale-2.jpg
435 ms
The-Georges-1.jpg
521 ms
GCDesign_Logo.svg
525 ms
Costa-Blanca-south.png
520 ms
Costa-Blanca-North.jpg
525 ms
Valencia.png
1016 ms
Costa-Calida-Murcia.jpg
206 ms
6SSp.gif
665 ms
1700759296860550
517 ms
5824766.js
365 ms
homeespana.com 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
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.
homeespana.com 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
homeespana.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Homeespana.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Homeespana.com 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.
homeespana.com
Open Graph data is detected on the main page of Home Espana. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: