3.2 sec in total
180 ms
2.5 sec
433 ms
Visit frenadol.es now to see the best up-to-date Frenadol content for Spain and also check out these interesting facts you probably never knew about frenadol.es
Combate eficazmente los síntomas de la gripe y el resfriado como fiebre, dolor de cabeza, estornudos, tos seca o dolor de garganta con Frenadol®.
Visit frenadol.esWe analyzed Frenadol.es page load time and found that the first response time was 180 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
frenadol.es performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value9.1 s
1/100
25%
Value8.5 s
18/100
10%
Value1,600 ms
12/100
30%
Value0.049
99/100
15%
Value17.2 s
4/100
10%
180 ms
230 ms
83 ms
169 ms
166 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 65% of them (62 requests) were addressed to the original Frenadol.es, 8% (8 requests) were made to Assets.adobedtm.com and 3% (3 requests) were made to Widget-cdn.rpxnow.com. The less responsive or slowest element that took the longest time to load (912 ms) belongs to the original domain Frenadol.es.
Page size can be reduced by 2.2 MB (62%)
3.5 MB
1.3 MB
In fact, the total size of Frenadol.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. 70% of websites need less resources to load. Javascripts take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 144.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 144.9 kB or 85% of the original size.
Potential reduce by 35.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. Frenadol images are well optimized though.
Potential reduce by 984.6 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 984.6 kB or 72% of the original size.
Potential reduce by 1.0 MB
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. Frenadol.es needs all CSS files to be minified and compressed as it can save up to 1.0 MB or 86% of the original size.
Number of requests can be reduced by 44 (48%)
92
48
The browser has sent 92 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Frenadol. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
frenadol.es
180 ms
www.frenadol.es
230 ms
css_3ijmoGqFgneVPsJPSaYstpw_yp4XL1A-AtIs6N2LjfM.css
83 ms
css_MPqh0nCRw4lA_uwl9mrj9OM44lkF6mmP-VCkZiGVsjU.css
169 ms
css_akCGZJVDEievy34qQLVqd5Bn3eAbSv4tNbLMFxC3A1I.css
166 ms
css_oujh0I7mpnywJ_WUlJd1NauEN0eBMzlRnZ_WhFRNlKM.css
164 ms
screen.css
246 ms
js_e11Wtlqyp6fGuwkH4TD7yxHFMqK2O6m6Eh9IVxKUFoE.js
329 ms
satelliteLib-a77040281e8ad94d1a2e4c30d4df757c9e6fed98.js
122 ms
js_NpX2cwCeepkWZZ194B6-ViyVBHleaYLOx5R9EWBOMRU.js
262 ms
janrain_capture_widget.js
259 ms
janrain.js
261 ms
janrain_share_widget.js
261 ms
js__oShtYdeoDT4xwwMz_-gfWEPpOpgZ99hucSduoKQbPk.js
324 ms
BrightcoveExperiences.js
12 ms
js
47 ms
js_-Dfu4GjIygLF58P8Ii6oYRVsb9uRzYXHccPw2Up2Rsg.js
324 ms
js_HO9cZEJWMGVwtSvARDPznk0NtrmZQdTBW_bgM-4RMoo.js
510 ms
js_TUcjGuld5bOccSVXZLORY-2qmwBTpcOBQchglJBUiE8.js
582 ms
janrain-social.min.js
21 ms
js_OKl7u83TIBeQyy80SnLrDi2gI6rtUEYPfoWy9O2cfJ4.js
324 ms
screen-blessed2.css
245 ms
screen-blessed1.css
271 ms
satellite-53299f495e4bd66166000812.js
44 ms
satellite-54cf99c96437370016c00000.js
70 ms
satellite-56bce3f264746d25ab001de3.js
83 ms
satellite-5364125bc80de2df990000a5.js
114 ms
satellite-5367cf849975ed0b470001fa.js
84 ms
tms.js
128 ms
mbox-contents-c29a324d2b3723ed58fb534cb4263bede2c0fae9.js
118 ms
target.js
76 ms
id
16 ms
standard
19 ms
id
38 ms
logo.png
126 ms
planazo-o-sofa.jpg
679 ms
gamma.png
514 ms
destacado-frenadol-complex.jpg
516 ms
chica-congestion.jpg
501 ms
chica-bufanda.jpg
501 ms
ico-footer-1_0.png
499 ms
gtm.js
100 ms
icons-s5b7e4f9203.png
449 ms
menu-leaf.png
450 ms
menu_icon_3236.png
452 ms
menu_icon_3231.png
454 ms
menu_icon_3226.png
455 ms
menu_icon_3221.png
455 ms
menu_icon_3216.png
457 ms
menu_icon_3241.png
459 ms
menu_icon_3246.png
459 ms
menu_icon_3251.png
461 ms
menu_icon_3261.png
462 ms
menu_icon_3271.png
461 ms
menu_icon_3276.png
462 ms
menu_icon_3281.png
623 ms
menu_icon_3286.png
623 ms
menu_icon_3291.png
624 ms
menu_icon_3296.png
625 ms
menu_icon_3306.png
625 ms
menu_icon_3311.png
647 ms
menu_icon_3316.png
646 ms
menu_icon_3321.png
648 ms
menu_icon_3326.png
646 ms
menu_icon_3341.png
647 ms
menu_icon_3346.png
647 ms
menu_icon_3351.png
738 ms
menu_icon_3356.png
739 ms
menu_icon_3361.png
738 ms
menu_icon_3371.png
738 ms
menu_icon_3376.png
738 ms
istokweb-regular-webfont.woff
912 ms
jquery.mousewheel.min.js
355 ms
s-code-contents-1d8ab93ceed12c00191ad960b48f86d3b6e05534.js
266 ms
analytics.js
254 ms
jjdev
239 ms
icomoon.ttf
382 ms
istokweb-bold-webfont.woff
456 ms
menu_icon_3381.png
378 ms
menu_icon_3386.png
378 ms
menu_icon_3391.png
374 ms
background-home.jpg
615 ms
janrain-social.css
99 ms
es-LA.js
140 ms
collect
87 ms
collect
113 ms
s08647497643250
65 ms
es
65 ms
es
9 ms
capture:login:share
18 ms
ga-audiences
104 ms
providers.css
75 ms
17c96fc4b9c8464d1c95cd785dd3120b.png
32 ms
27huyg6vmfwr27srrw3agddm7cj949aq.js
79 ms
widgets.css
31 ms
en-US.js
30 ms
frenadol.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-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
frenadol.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
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
frenadol.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 doesn't use 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 Frenadol.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 Frenadol.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.
frenadol.es
Open Graph description is not detected on the main page of Frenadol. 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: