9.1 sec in total
427 ms
8.3 sec
336 ms
Welcome to verfarma.com homepage info - get ready to check Verfarma best content for Spain right away, or after learning these important things about verfarma.com
Comunidad de Estudiantes y Profesionales del sector Farmacéutico. Foro, blog, artículos y servicios relacionados con el sector farmacéutico.
Visit verfarma.comWe analyzed Verfarma.com page load time and found that the first response time was 427 ms and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
verfarma.com performance score
name
value
score
weighting
Value5.2 s
8/100
10%
Value8.7 s
1/100
25%
Value11.1 s
6/100
10%
Value6,710 ms
0/100
30%
Value0
100/100
15%
Value17.5 s
4/100
10%
427 ms
3769 ms
2057 ms
1383 ms
914 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 4% of them (4 requests) were addressed to the original Verfarma.com, 23% (23 requests) were made to Verfarma.net and 20% (20 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (3.8 sec) belongs to the original domain Verfarma.com.
Page size can be reduced by 687.4 kB (29%)
2.4 MB
1.7 MB
In fact, the total size of Verfarma.com main page is 2.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 52.3 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 52.3 kB or 81% 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. Verfarma images are well optimized though.
Potential reduce by 534.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 534.6 kB or 57% of the original size.
Potential reduce by 69.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. Verfarma.com needs all CSS files to be minified and compressed as it can save up to 69.3 kB or 83% of the original size.
Number of requests can be reduced by 43 (49%)
88
45
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Verfarma. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
verfarma.com
427 ms
www.verfarma.com
3769 ms
be41f7f9a46f61c68a8ffcec4ae2dea0.css
2057 ms
style.css
1383 ms
responsive.css
914 ms
all.js
86 ms
adsbygoogle.js
23 ms
b0255f17466dc57ad003f3677c3aee1e.js
1800 ms
logo.png
454 ms
ico_buscar.png
453 ms
icono_twitter.png
454 ms
icono_facebook.png
453 ms
icono_loginbutton.png
1157 ms
verkia.gif
550 ms
dolor.JPG
729 ms
implante-coclear.jpg
788 ms
esalud.jpg
784 ms
verkia.jpg
731 ms
verkia.jpg
782 ms
loader.gif
1000 ms
607 ms
ico_subir_recurso_anim.png
995 ms
ico_pdf_small.png
995 ms
ico_ppt_small.png
888 ms
xd_arbiter.php
376 ms
xd_arbiter.php
561 ms
bentonsans-light-webfont.woff
990 ms
ico_ir_top.png
1050 ms
cse.js
270 ms
analytics.js
193 ms
ca-pub-1147296346748286.js
356 ms
zrt_lookup.html
437 ms
show_ads_impl.js
183 ms
increase_hits.php
447 ms
ping
340 ms
abstract09.gif
700 ms
smokey10.gif
1160 ms
noavatar.png
784 ms
pla
202 ms
collect
97 ms
cse.js
254 ms
ads
294 ms
like_box.php
179 ms
osd.js
119 ms
collect
162 ms
ads
337 ms
dolor.JPG
626 ms
kyEKgjk51ZE.css
106 ms
xgj7bXhJNEH.css
214 ms
kE_Z8j4XNUS.css
286 ms
q68gy-v_YMF.js
349 ms
FJmpeSpHpjS.js
385 ms
0wM5s1Khldu.js
370 ms
1bNoFZUdlYZ.js
346 ms
OloiM1PZafe.js
369 ms
LTv6ZK-5zxz.js
478 ms
1FCa-btixu2.js
476 ms
Oagsvfb4VWi.js
477 ms
pObvZSrFc_4.js
476 ms
Kt4tkgSRvHH.js
475 ms
H3EKDTObx05.js
473 ms
eR-qA8bp1RM.js
575 ms
ga-audiences
42 ms
jsapi
43 ms
default+es.css
4 ms
default.css
26 ms
default+es.I.js
25 ms
default.css
109 ms
css
351 ms
m_js_controller.js
335 ms
abg.js
426 ms
css
359 ms
async-ads.js
157 ms
google_custom_search_watermark.gif
114 ms
small-logo.png
101 ms
search_box_icon.png
106 ms
bentonsans-light-webfont.ttf
452 ms
favicon
323 ms
googlelogo_color_112x36dp.png
319 ms
nessie_icon_tiamat_white.png
127 ms
x_button_blue2.png
229 ms
12193297_938723096214658_4439031407823638546_n.png
515 ms
10013935_623977537689217_1138721939_n.png
533 ms
10649895_1051596231559186_6601341237072375963_n.jpg
550 ms
12871493_163442350713382_1090330919493339412_n.jpg
567 ms
12662030_1261123433904054_386997033423151606_n.jpg
576 ms
10888478_772740949441476_5874113431234843780_n.jpg
566 ms
12227634_10208148921345917_9076343685034206170_n.jpg
567 ms
12806102_1591990714389676_4750322771568954575_n.jpg
568 ms
11698653_10206113296249481_3019780584214594565_n.jpg
568 ms
wL6VQj7Ab77.png
193 ms
s7jcwEQH7Sx.png
192 ms
_aijTyevf54tkVDLy-dlnKCWcynf_cDxXwCLxiixG1c.ttf
232 ms
s
184 ms
gxbPuQdXIZP.png
62 ms
fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js
12 ms
I6-MnjEovm5.js
27 ms
pQrUxxo5oQp.js
27 ms
ui
21 ms
verfarma.com 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
ARIA IDs are not unique
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
verfarma.com 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
Missing source maps for large first-party JavaScript
Issues were logged in the Issues panel in Chrome Devtools
verfarma.com SEO score
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
ES
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Verfarma.com 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 Verfarma.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.
verfarma.com
Open Graph description is not detected on the main page of Verfarma. 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: