6 sec in total
431 ms
5.1 sec
398 ms
Welcome to nexia.es homepage info - get ready to check Nexia best content for Spain right away, or after learning these important things about nexia.es
Creando espacios acogedores que conectan a las personas con la tecnología
Visit nexia.esWe analyzed Nexia.es page load time and found that the first response time was 431 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
nexia.es performance score
name
value
score
weighting
Value1.4 s
97/100
10%
Value3.3 s
70/100
25%
Value8.6 s
17/100
10%
Value2,100 ms
7/100
30%
Value0.077
95/100
15%
Value10.0 s
26/100
10%
431 ms
1157 ms
799 ms
112 ms
371 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 66% of them (87 requests) were addressed to the original Nexia.es, 10% (13 requests) were made to Fonts.gstatic.com and 3% (4 requests) were made to W.sharethis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Nexia.es.
Page size can be reduced by 1.5 MB (42%)
3.5 MB
2.0 MB
In fact, the total size of Nexia.es main page is 3.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. 75% 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.8 MB which makes up the majority of the site volume.
Potential reduce by 55.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. This page needs HTML code to be minified as it can gain 13.3 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 55.5 kB or 82% of the original size.
Potential reduce by 157.9 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. Nexia images are well optimized though.
Potential reduce by 926.3 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 926.3 kB or 73% of the original size.
Potential reduce by 327.0 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. Nexia.es needs all CSS files to be minified and compressed as it can save up to 327.0 kB or 82% of the original size.
Number of requests can be reduced by 53 (47%)
113
60
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nexia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
nexia.es
431 ms
www.nexia.es
1157 ms
799 ms
font-awesome.min.css
112 ms
jquery-1.7.2.min.js
371 ms
ie.js
219 ms
jquery.easing.1.3.js
218 ms
modernizr.custom.js
226 ms
jquery.polyglot.language.switcher.js
226 ms
ddlevelsmenu.js
218 ms
tinynav.min.js
322 ms
jquery.validate.min.js
325 ms
jquery.flexslider-min.js
326 ms
jquery.jcarousel.min.js
333 ms
jquery.ui.totop.min.js
332 ms
jquery-ui-1.10.1.custom.min.js
758 ms
jquery.fancybox.pack.js
435 ms
jquery.cycle.all.js
438 ms
jquery.fitvids.js
440 ms
jquery.tweet.js
442 ms
jflickrfeed.min.js
470 ms
jquery.quicksand.js
541 ms
jquery.touchSwipe.min.js
547 ms
jquery.datetimepicker.js
660 ms
jquery.magnific-popup.min.js
550 ms
custom.js
579 ms
style.min.css
649 ms
buttons.js
10 ms
jquery.validate.js
656 ms
css
27 ms
css
40 ms
css
47 ms
html5-reset.css
119 ms
polyglot-language-switcher.css
110 ms
flexslider.css
118 ms
jquery.fancybox.css
116 ms
mediaelementplayer.css
110 ms
shortcodes.css
113 ms
nexia-partner-for-led-technology.jpg
283 ms
nexiahigh.gif
281 ms
slider_nueva_web_44.png
962 ms
slider_nueva_web_40.png
901 ms
slider_nueva_web_19-v1.jpg
829 ms
slider_nueva_web_33.jpg
848 ms
calculadora-ahorro.jpg
419 ms
calculadora-tension-tiras-led.jpg
471 ms
pull_out.jpg
607 ms
infinity_system_suspendida_-_blanco-v1.jpg
617 ms
bcn120bis.jpg
801 ms
prosq.jpg
813 ms
700_collins_st_project_05.png
1048 ms
cafeteria_jonquera_serie_drac.png
1188 ms
lb2016-v1-v1.png
997 ms
lb2016-v1.png
944 ms
logo-amec-footer.jpg
1004 ms
logo-cambra-footer.jpg
1049 ms
logo-raees-footer.jpg
1067 ms
logo-rohs-footer.jpg
1101 ms
logo-cicat-footer.jpg
1118 ms
logo-blc-footer.jpg
1159 ms
logo_nexia_footer.jpg
1159 ms
logo_dowhilestudio_footer.jpg
1173 ms
dc.js
38 ms
lock24.png
1200 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
13 ms
DXI1ORHCpsQm3Vp6mXoaTYnF5uFdDttMLvmWuJdhhgs.ttf
13 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
24 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
23 ms
EInbV5DfGHOiMmvb1Xr-honF5uFdDttMLvmWuJdhhgs.ttf
24 ms
dropdown-menu.png
1197 ms
phone.png
1230 ms
mail.png
1228 ms
0IZPA9DbzKXnGZABsAivT50EAVxt0G0biEntp43Qt6E.ttf
30 ms
__utm.gif
202 ms
search.png
1117 ms
ahorro.jpg
1124 ms
eficencia.jpg
1144 ms
greenenergy.jpg
1165 ms
tecnologia.jpg
1216 ms
overlay-link.png
1217 ms
post-standard.png
1229 ms
flag-16.png
1245 ms
getAllAppDefault.esi
80 ms
ga-audiences
79 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
17 ms
PRmiXeptR36kaC0GEAetxrfB31yxOzP-czbf6AAKCVo.ttf
18 ms
PRmiXeptR36kaC0GEAetxi8cqLH4MEiSE0ROcU-qHOA.ttf
16 ms
PRmiXeptR36kaC0GEAetxp_TkvowlIOtbR7ePgFOpF4.ttf
16 ms
PRmiXeptR36kaC0GEAetxlDMrAYtoOisqqMDW9M_Mqc.ttf
18 ms
error-16.png
1157 ms
sqMHzrpands
112 ms
getSegment.php
27 ms
checkOAuth.esi
12 ms
t.dhj
18 ms
t.dhj
46 ms
pencil-footer.png
1067 ms
cm
51 ms
x35248
380 ms
www-embed-player-vflfNyN_r.css
60 ms
www-embed-player.js
104 ms
base.js
171 ms
s-3271.xgi
33 ms
home-footer.png
1018 ms
33 ms
hbpix
116 ms
245 ms
pixel
202 ms
phone-footer.png
901 ms
mail-footer.png
901 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
37 ms
ad_status.js
108 ms
xrefid.xgi
44 ms
pixel
83 ms
twitter-circular.png
750 ms
facebook-circular.png
779 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
62 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
65 ms
google-circular.png
772 ms
linkedin-circular.png
734 ms
2981
33 ms
instagram-circular.png
728 ms
pinterest-circular.png
726 ms
youtube-circular.png
740 ms
vimeo-circular.png
707 ms
gb.png
721 ms
arrow-down-lg-switcher.png
684 ms
arrows.png
732 ms
scroll-top.png
737 ms
index.2d85e55d89f85ae69e4f2ca5ab9438b7.html
26 ms
buttons.ab966a004186897711de4a5ed256c924.css
16 ms
stcommon.2b05accc08f1ee42fe1983647ab923ea.js
4 ms
st.1188278743c14064d5e8ae56c8ada29c.js
7 ms
nexia.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
Form elements do not have associated labels
nexia.es 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
nexia.es 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nexia.es 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 Nexia.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.
nexia.es
Open Graph description is not detected on the main page of Nexia. 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: