3.6 sec in total
403 ms
2.9 sec
279 ms
Welcome to prenatal.es homepage info - get ready to check Prenatal best content for Spain right away, or after learning these important things about prenatal.es
Visit prenatal.esWe analyzed Prenatal.es page load time and found that the first response time was 403 ms and then it took 3.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
prenatal.es performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value26.0 s
0/100
25%
Value29.7 s
0/100
10%
Value40,480 ms
0/100
30%
Value0.227
55/100
15%
Value68.6 s
0/100
10%
403 ms
459 ms
147 ms
87 ms
148 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 65% of them (54 requests) were addressed to the original Prenatal.es, 11% (9 requests) were made to Static.xx.fbcdn.net and 5% (4 requests) were made to Track.adform.net. The less responsive or slowest element that took the longest time to load (824 ms) belongs to the original domain Prenatal.es.
Page size can be reduced by 788.0 kB (53%)
1.5 MB
706.0 kB
In fact, the total size of Prenatal.es main page is 1.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. 55% of websites need less resources to load. Images take 755.0 kB which makes up the majority of the site volume.
Potential reduce by 44.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. This page needs HTML code to be minified as it can gain 6.8 kB, which is 12% 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 44.7 kB or 81% of the original size.
Potential reduce by 217.0 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, Prenatal needs image optimization as it can save up to 217.0 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 339.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 339.2 kB or 73% of the original size.
Potential reduce by 187.1 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. Prenatal.es needs all CSS files to be minified and compressed as it can save up to 187.1 kB or 87% of the original size.
Number of requests can be reduced by 33 (42%)
78
45
The browser has sent 78 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prenatal. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
prenatal.es
403 ms
www.prenatal.es
459 ms
home.html
147 ms
home.html
87 ms
reset.css
148 ms
core.css
232 ms
owl.carousel.css
165 ms
plusone.js
85 ms
jquery-1.9.1.min.js
354 ms
jquery.cycle.all.min.js
297 ms
core.js
167 ms
cart_checkout.js
337 ms
owl.carousel.js
349 ms
cb=gapi.loaded_0
21 ms
442 ms
logoprenatal.gif
91 ms
header_loader.gif
90 ms
underconstrucctionES.jpg
335 ms
SlidePV16ES.jpg
327 ms
CharlasES.jpg
246 ms
GuiacasaES.jpg
185 ms
GuiapaseoES.jpg
231 ms
GuiaindispensablesES.jpg
230 ms
box_corredino_esNew.jpg
329 ms
AAbox-camerette-es.jpg
384 ms
box_prenatal_card_es16.jpg
386 ms
box_video_es.jpg
327 ms
box_centrostudi_es_new.jpg
409 ms
box_charlas_es_ok.jpg
411 ms
box_news_es_new.jpg
490 ms
android.gif
416 ms
itunes.gif
461 ms
norton.gif
462 ms
gtm.js
82 ms
bg_section.png
652 ms
bg_nav_main_active.gif
485 ms
userInfo.do
685 ms
FSLolaBoldItalic.woff
519 ms
EffraMedium.woff
585 ms
moreViewsBackground.jpg
538 ms
bg_arrow_bullet_grey.gif
539 ms
bg_footer.png
613 ms
fb.gif
572 ms
tt.gif
574 ms
pi.gif
614 ms
yt.gif
652 ms
flag_italy.gif
655 ms
flag_cyprus.gif
655 ms
flag_netherlands.gif
689 ms
flag_greece.gif
691 ms
flag_portugal.gif
708 ms
flag_spain.gif
732 ms
close_cookie.png
733 ms
like.php
102 ms
bg_slider_prev.jpg
824 ms
slider_ES.js
378 ms
analytics.js
27 ms
linkid.js
16 ms
collect
76 ms
collect
76 ms
collect
83 ms
bg_slider_next.jpg
724 ms
vpd1GgSCNsd.css
301 ms
M0DWM6a_9ro.css
373 ms
AdP_CKHZFBh.css
445 ms
_rx8naC75Dy.js
659 ms
TuuohdynnB6.js
510 ms
d6RcVOf4_V3.js
679 ms
phKJLmGTCBO.js
657 ms
bg_slider_pause.png
679 ms
bg_slider_pager.png
683 ms
204 ms
105 ms
249 ms
conversion.js
16 ms
37 ms
100 ms
Bw8qRoQ9D-v.js
74 ms
Xz08Qlfw8qz.js
206 ms
print.css
78 ms
slider_ES.js
87 ms
middle_bg_whiteb.gif
252 ms
BannerSuperTopES_Off.jpg
400 ms
prenatal.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
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
[id] attributes on active, focusable elements are not unique
Some elements have a [tabindex] value greater than 0
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
Image elements do not have [alt] attributes
Links do not have a discernible name
<object> elements do not have alternate text
prenatal.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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
prenatal.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
Image elements do not have [alt] attributes
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 Prenatal.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 Prenatal.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.
prenatal.es
Open Graph description is not detected on the main page of Prenatal. 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: