Tools & Wizards About Us
vademecum.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 91% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

vademecum.com

Vademecum España para el médico, farmacéutico y particular

Page Load Speed

3 sec in total

First Response

210 ms

Resources Loaded

2.6 sec

Page Rendered

211 ms

vademecum.com screenshot

About Website

Welcome to vademecum.com homepage info - get ready to check Vademecum best content for Spain right away, or after learning these important things about vademecum.com

Vademecum España ofrece información online completa y sin descargar sobre medicamentos, enfermedades, farmacia y laboratorios farmacéuticos.

Visit vademecum.com

Key Findings

We analyzed Vademecum.com page load time and found that the first response time was 210 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

vademecum.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

26/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value3,470 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.012

100/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

vademecum.com

210 ms

www.vademecum.com

378 ms

jquery-3.4.1.min.js

42 ms

popper.min.js

87 ms

bootstrap.min.js

58 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 27% of them (18 requests) were addressed to the original Vademecum.com, 12% (8 requests) were made to Pagead2.googlesyndication.com and 12% (8 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (623 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 179.4 kB (15%)

Content Size

1.2 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Vademecum.com main page is 1.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. 70% of websites need less resources to load. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 39.5 kB

  • Original 50.5 kB
  • After minification 47.8 kB
  • After compression 11.0 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 39.5 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 55 B

  • Original 92.0 kB
  • After minification 91.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. Vademecum images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 136.5 kB

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 899.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 136.5 kB or 13% of the original size.

CSS Optimization

-17%

Potential reduce by 3.4 kB

  • Original 19.4 kB
  • After minification 19.4 kB
  • After compression 16.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. Vademecum.com needs all CSS files to be minified and compressed as it can save up to 3.4 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 43 (75%)

Requests Now

57

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 57 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Vademecum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

vademecum.com

vademecum.com

210 ms

www.vademecum.com

www.vademecum.com

378 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

42 ms

popper.min.js

popper.min.js

87 ms

bootstrap.min.js

bootstrap.min.js

58 ms

comun.min.js

comun.min.js

227 ms

js

js

94 ms

gpt.js

gpt.js

125 ms

adsbygoogle.js

adsbygoogle.js

223 ms

bootstrap.min.css

bootstrap.min.css

64 ms

comun.min.css

comun.min.css

347 ms

adsbygoogle.js

adsbygoogle.js

358 ms

pubads_impl.js

pubads_impl.js

70 ms

logo-vademecum.png

logo-vademecum.png

125 ms

flag-es.png

flag-es.png

150 ms

flag-ar.png

flag-ar.png

231 ms

flag-cl.png

flag-cl.png

231 ms

flag-co.png

flag-co.png

232 ms

flag-us.png

flag-us.png

296 ms

flag-mx.png

flag-mx.png

314 ms

flag-pe.png

flag-pe.png

318 ms

flag-ve.png

flag-ve.png

316 ms

imagela-es.jpg

imagela-es.jpg

428 ms

show_ads_impl.js

show_ads_impl.js

324 ms

8296571

8296571

70 ms

font-awesome.min.css

font-awesome.min.css

195 ms

css

css

38 ms

cse.js

cse.js

106 ms

background-home.jpg

background-home.jpg

183 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

77 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

77 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

78 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

252 ms

zrt_lookup.html

zrt_lookup.html

72 ms

ads

ads

623 ms

cse_element__es.js

cse_element__es.js

40 ms

default+es.css

default+es.css

90 ms

default.css

default.css

93 ms

ads

ads

406 ms

ads

ads

418 ms

async-ads.js

async-ads.js

34 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

54 ms

data=6xfQr28NqZDEGpvUtGxoHuFqbzdornTXLVbY-YzB2qAbskxz096Wwx6Dr4DKb_bO1KP3VrIUKgfd1KWUlyGD_BOkmeNGhnON789sl4Sh95FucIrm-RGDv5sS

data=6xfQr28NqZDEGpvUtGxoHuFqbzdornTXLVbY-YzB2qAbskxz096Wwx6Dr4DKb_bO1KP3VrIUKgfd1KWUlyGD_BOkmeNGhnON789sl4Sh95FucIrm-RGDv5sS

202 ms

load_preloaded_resource.js

load_preloaded_resource.js

179 ms

abg_lite.js

abg_lite.js

181 ms

window_focus.js

window_focus.js

180 ms

qs_click_protection.js

qs_click_protection.js

43 ms

ufs_web_display.js

ufs_web_display.js

41 ms

bbae3fd3506d8d9338f85d10ea9db8af.js

bbae3fd3506d8d9338f85d10ea9db8af.js

208 ms

icon.png

icon.png

34 ms

css

css

28 ms

reactive_library.js

reactive_library.js

147 ms

ads

ads

199 ms

ads

ads

275 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrwEIJllpyw.ttf

5 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrw2IJllpyw.ttf

6 ms

activeview

activeview

158 ms

J23fcjYtRQif16sy8ro7eXEnEArCvdqXEoVeVS6IgPU.js

J23fcjYtRQif16sy8ro7eXEnEArCvdqXEoVeVS6IgPU.js

23 ms

s

s

71 ms

feedback_grey600_24dp.png

feedback_grey600_24dp.png

8 ms

fullscreen_api_adapter.js

fullscreen_api_adapter.js

74 ms

interstitial_ad_frame.js

interstitial_ad_frame.js

79 ms

settings_grey600_24dp.png

settings_grey600_24dp.png

80 ms

8741269557722925928

8741269557722925928

34 ms

css

css

17 ms

activeview

activeview

107 ms

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrzjJ5llpyw.ttf

4Ua_rENHsxJlGDuGo1OIlJfC6l_24rlCK1Yo_Iqcsih3SAyH6cAwhX9RFD48TE63OOYKtrzjJ5llpyw.ttf

94 ms

Accessibility Review

vademecum.com accessibility score

97

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Best Practices

vademecum.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

vademecum.com SEO score

92

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Vademecum.com 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 Vademecum.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.

Social Sharing Optimization

vademecum.com

Open Graph description is not detected on the main page of Vademecum. 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: