6.4 sec in total
295 ms
5.8 sec
263 ms
Welcome to nexusgeografics.com homepage info - get ready to check Nexus Geografics best content right away, or after learning these important things about nexusgeografics.com
En Nexus Geographics somos una empresa especializada en geolocalización y adaptamos mapas inteligentes e información geográfica a las necesidades de empresas y administraciones
Visit nexusgeografics.comWe analyzed Nexusgeografics.com page load time and found that the first response time was 295 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
nexusgeografics.com performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value7.6 s
3/100
25%
Value6.4 s
40/100
10%
Value360 ms
72/100
30%
Value0.01
100/100
15%
Value7.8 s
45/100
10%
295 ms
510 ms
98 ms
188 ms
190 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Nexusgeografics.com, 66% (67 requests) were made to Nexusgeographics.com and 16% (16 requests) were made to Api.cercalia.com. The less responsive or slowest element that took the longest time to load (2.5 sec) relates to the external source Api.cercalia.com.
Page size can be reduced by 394.1 kB (18%)
2.2 MB
1.8 MB
In fact, the total size of Nexusgeografics.com main page is 2.2 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. 40% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 32.7 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 32.7 kB or 79% of the original size.
Potential reduce by 14.7 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. Nexus Geografics images are well optimized though.
Potential reduce by 176.5 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 176.5 kB or 71% of the original size.
Potential reduce by 170.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. Nexusgeografics.com needs all CSS files to be minified and compressed as it can save up to 170.3 kB or 84% of the original size.
Number of requests can be reduced by 61 (61%)
100
39
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nexus Geografics. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 40 to 1 for CSS and as a result speed up the page load time.
nexusgeografics.com
295 ms
www.nexusgeographics.com
510 ms
system.base.css
98 ms
system.menus.css
188 ms
system.messages.css
190 ms
system.theme.css
192 ms
field.css
192 ms
node.css
192 ms
search.css
193 ms
user.css
280 ms
views.css
281 ms
ckeditor.css
285 ms
colorbox_style.css
287 ms
ctools.css
287 ms
nice_menus.css
288 ms
nice_menus_default.css
372 ms
tagclouds.css
373 ms
views_slideshow.css
379 ms
views_slideshow_cycle.css
379 ms
locale.css
379 ms
eu_cookie_compliance.css
380 ms
html-reset.css
463 ms
wireframes.css
465 ms
layout-fixed.css
472 ms
page-backgrounds.css
473 ms
tabs.css
473 ms
pages.css
473 ms
blocks.css
555 ms
navigation.css
556 ms
views-styles.css
565 ms
nodes.css
566 ms
comments.css
566 ms
forms.css
566 ms
fields.css
647 ms
print.css
649 ms
css_injector_2.css
660 ms
css_injector_4.css
661 ms
css_injector_5.css
661 ms
css_injector_10.css
580 ms
js_UWQINlriydSoeSiGQxToOUdv493zEa7dpsXC1OtYlZU.js
754 ms
js_KxePwYyIYxc2teh76BRwTx8rE6bPl7sH3mHrBGvvK4k.js
766 ms
colorbox-aviso.js
575 ms
js_I8yX6RYPZb7AtMcDUA3QKDZqVkvEn35ED11_1i7vVpc.js
575 ms
js_paiTaEsc1HNeBS2rkLc1NrprKrFnApv70kuY8awAaTI.js
575 ms
analytics.js
103 ms
controlMapExample.html
377 ms
bottom-line.gif
109 ms
logo-nexus.png
108 ms
arrow-down.gif
109 ms
mou-te-main-esp.jpg
419 ms
abertis-promo-web.jpg
378 ms
slide-web-turisme.jpg
575 ms
slide-web-andorra-es.jpg
560 ms
Slide16_0.jpg
953 ms
Slide3.png
475 ms
slide14.jpg
754 ms
Slide13-es_0.png
512 ms
Slide12.jpg
760 ms
Slide1.jpg
703 ms
pager.gif
651 ms
idees_icons.png
668 ms
cercalia-home.png
745 ms
mwc16_logo.png
763 ms
1_0.jpg
797 ms
ajuntament-de-barcelona%20270x90.jpg
838 ms
feed.png
845 ms
twitter-icon.png
853 ms
picasa-icon.png
857 ms
linkedin-icon.png
891 ms
youtube-icon.png
929 ms
collect
24 ms
cercalia.js
2549 ms
jquery-ui-1.10.4.min.css
113 ms
jquery-ui-1.10.4.cercalia.css
223 ms
ol.css
220 ms
RequestsAPI
334 ms
traffic_es.json
111 ms
bg-toolbar.png
111 ms
ui-bg_flat_75_E94B3B_40x100.png
112 ms
cercalia-big-icons_ffffff.png
112 ms
ui-icons_FFFFFF_256x240.png
194 ms
north.png
219 ms
zoom-icons.gif
220 ms
ui-bg_flat_0_E0E0E0_40x100.png
219 ms
ui-bg_flat_75_ffffff_40x100.png
220 ms
RequestsAPI
196 ms
24.png
370 ms
23.png
389 ms
25.png
375 ms
23.png
386 ms
23.png
405 ms
23.png
404 ms
23.png
275 ms
25.png
271 ms
25.png
270 ms
25.png
374 ms
25.png
268 ms
24.png
266 ms
24.png
372 ms
24.png
258 ms
24.png
255 ms
logo.gif
454 ms
nexusgeografics.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
<object> elements do not have alternate text
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
nexusgeografics.com 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
nexusgeografics.com 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
EN
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nexusgeografics.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Spanish language. Our system also found out that Nexusgeografics.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.
nexusgeografics.com
Open Graph description is not detected on the main page of Nexus Geografics. 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: