2.6 sec in total
469 ms
1.7 sec
368 ms
Click here to check amazing Verbascum content for France. Otherwise, check out these important facts you probably never knew about verbascum.org
Visit verbascum.orgWe analyzed Verbascum.org page load time and found that the first response time was 469 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
verbascum.org performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value4.9 s
29/100
25%
Value10.6 s
7/100
10%
Value1,920 ms
8/100
30%
Value0
100/100
15%
Value14.2 s
9/100
10%
469 ms
109 ms
60 ms
81 ms
176 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 18% of them (11 requests) were addressed to the original Verbascum.org, 21% (13 requests) were made to S0.2mdn.net and 10% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (647 ms) relates to the external source Gallery.netbaran.com.
Page size can be reduced by 201.0 kB (22%)
912.7 kB
711.7 kB
In fact, the total size of Verbascum.org main page is 912.7 kB. 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. Images take 629.1 kB which makes up the majority of the site volume.
Potential reduce by 14.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. 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 14.7 kB or 69% of the original size.
Potential reduce by 45.7 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. Verbascum images are well optimized though.
Potential reduce by 108.8 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 108.8 kB or 49% of the original size.
Potential reduce by 31.8 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. Verbascum.org needs all CSS files to be minified and compressed as it can save up to 31.8 kB or 83% of the original size.
Number of requests can be reduced by 17 (32%)
53
36
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Verbascum. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 18 to 1 for JavaScripts and as a result speed up the page load time.
verbascum.org
469 ms
wp-emoji-release.min.js
109 ms
css
60 ms
style.css
81 ms
jquery.js
176 ms
jquery-migrate.min.js
77 ms
adsbygoogle.js
20 ms
c.aspx
155 ms
navigation.js
84 ms
wp-embed.min.js
77 ms
photogallery-logo.jpg
647 ms
logo_small_whitespaceleft.gif
182 ms
cs--logo1.jpg
532 ms
flora-logo.jpg
540 ms
tree_logo.jpg
517 ms
xstat.aspx
177 ms
bg2-1.jpg
173 ms
header2.jpg
50 ms
IMG_0118-v.jpg
173 ms
verbascum-songaricum1.jpg
173 ms
ca-pub-8507639747863136.js
54 ms
zrt_lookup.html
48 ms
show_ads_impl.js
72 ms
u-WUoqrET9fUeobQW7jkRaCWcynf_cDxXwCLxiixG1c.ttf
43 ms
k3k702ZOKiLJc3WVjuplzNqQynqKV_9Plp7mupa0S4g.ttf
63 ms
PRmiXeptR36kaC0GEAetxiBnJMIPt0VoltfALX9gDFQ.ttf
67 ms
xjAJXh38I15wypJXxuGMBl02b4v3fUxqf9CZJ1qUoIA.ttf
150 ms
ads
324 ms
osd.js
35 ms
ads
257 ms
tree_logo.jpg
180 ms
cs--logo1.jpg
191 ms
flora-logo.jpg
181 ms
s_0R1j28YW9N_1766118946.html
47 ms
11122066921707622037
74 ms
abg.js
76 ms
m_js_controller.js
87 ms
googlelogo_color_112x36dp.png
45 ms
cl
96 ms
creative_add_on.js
163 ms
s
25 ms
x_button_blue2.png
24 ms
modernizr_2.8.3_ec185bb44fe5e6bf7455d6e8ef37ed0e_no-classes.js
49 ms
lidar.js
13 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
27 ms
index.html
20 ms
surly.js
132 ms
styles.css
4 ms
faucet0.png
11 ms
faucet1.png
16 ms
faucet2.png
21 ms
t0.png
23 ms
t0_white.png
22 ms
t1.png
20 ms
logo.svg
20 ms
cta_bg.png
23 ms
cta_text.png
22 ms
bathroom_bg.png
6 ms
ba.html
29 ms
4.gif
58 ms
2532.js
54 ms
verbascum.org 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
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
verbascum.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
verbascum.org 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Verbascum.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Verbascum.org 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.
verbascum.org
Open Graph description is not detected on the main page of Verbascum. 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: