5.8 sec in total
492 ms
5 sec
257 ms
Click here to check amazing Nectar content for Spain. Otherwise, check out these important facts you probably never knew about nectar.es
Accede a nuestra web para encontrar las clínicas y profesionales de Néctar más cercanos a ti
Visit nectar.esWe analyzed Nectar.es page load time and found that the first response time was 492 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
nectar.es performance score
name
value
score
weighting
Value4.1 s
21/100
10%
Value7.4 s
4/100
25%
Value6.2 s
44/100
10%
Value390 ms
69/100
30%
Value0.001
100/100
15%
Value7.5 s
48/100
10%
492 ms
828 ms
66 ms
199 ms
297 ms
Our browser made a total of 76 requests to load all elements on the main page. We found that 72% of them (55 requests) were addressed to the original Nectar.es, 4% (3 requests) were made to Cdn.luckyorange.net and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.8 sec) belongs to the original domain Nectar.es.
Page size can be reduced by 1.1 MB (65%)
1.7 MB
586.7 kB
In fact, the total size of Nectar.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. 50% of websites need less resources to load. Javascripts take 904.1 kB which makes up the majority of the site volume.
Potential reduce by 32.2 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 7.3 kB, which is 18% 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 32.2 kB or 77% of the original size.
Potential reduce by 31.2 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. Obviously, Nectar needs image optimization as it can save up to 31.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 645.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 645.5 kB or 71% of the original size.
Potential reduce by 379.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. Nectar.es needs all CSS files to be minified and compressed as it can save up to 379.7 kB or 85% of the original size.
Number of requests can be reduced by 48 (71%)
68
20
The browser has sent 68 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Nectar. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 30 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
nectar.es
492 ms
www.nectar.es
828 ms
css
66 ms
jquery-1.10.2.min.js
199 ms
jquery-migrate-1.2.1.min.js
297 ms
bootstrap.min.css
519 ms
style.css
431 ms
box-shadows.css
328 ms
font-awesome.min.css
42 ms
line-icons.css
328 ms
red.css
330 ms
Nectar.css
394 ms
custom.css
425 ms
cookiecuttr.css
426 ms
tarificador.css
441 ms
sky-forms.css
491 ms
sky-forms-main.css
528 ms
layerslider.css
529 ms
WebResource.axd
530 ms
ScriptResource.axd
626 ms
ScriptResource.axd
592 ms
bootstrap.min.js
612 ms
common.js
619 ms
html2canvas.min.js
620 ms
AnalyticsEvents.js
625 ms
CommonCia.js
686 ms
jquery-ui.min.js
712 ms
jquery.validate.min.js
717 ms
jquery.maskedinput.min.js
717 ms
jquery.maskmoney.js
722 ms
jquery.cookie.js
721 ms
jquery.cookiecuttr.js
782 ms
greensock.js
810 ms
layerslider.transitions.js
814 ms
layerslider.kreaturamedia.jquery.js
915 ms
index.js
821 ms
nectar.js
821 ms
app.js
878 ms
conversion.js
45 ms
app.css
489 ms
plugins.css
495 ms
ie8.css
498 ms
animate.css
497 ms
css
15 ms
CBE25A93A6D42E5-70x70.png
385 ms
logo-nectar.png
115 ms
ciudad.gif
2765 ms
ciudad-movil.png
216 ms
movil-ctc.gif
442 ms
calcula-tu-seguro.png
117 ms
encuentra-tu-medico.png
115 ms
seguro-medico-adaptado.png
215 ms
aldeasinfantileshome-nectar.jpg
423 ms
compania-del-grupo-hna.jpg
312 ms
actualizando.gif
307 ms
ciudad-fondo.gif
236 ms
HelveticaNeueLight.woff
389 ms
HelveticaNeueLTStdRoman.woff
294 ms
fontawesome-webfont.woff
18 ms
HelveticaNeueThin.woff
305 ms
iconos-redes-sociales.png
383 ms
analytics.js
79 ms
63 ms
w.js
69 ms
fbevents.js
343 ms
47 ms
clickstream.min.js
75 ms
collect
34 ms
collect
79 ms
storage.luckyorange.net
166 ms
ga-audiences
19 ms
settings.luckyorange.net
177 ms
95 ms
88 ms
mutation.min.js
13 ms
reset.css
39 ms
nectar.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
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.
nectar.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
nectar.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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nectar.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Nectar.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.
nectar.es
Open Graph description is not detected on the main page of Nectar. 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: