2.6 sec in total
195 ms
2.1 sec
303 ms
Visit kew.org now to see the best up-to-date Kew content for Brazil and also check out these interesting facts you probably never knew about kew.org
Discover a world of science hiding behind our beautiful botanical collections filled with over 40,000 living plants
Visit kew.orgWe analyzed Kew.org page load time and found that the first response time was 195 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
kew.org performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value11.1 s
0/100
25%
Value4.8 s
66/100
10%
Value130 ms
96/100
30%
Value0.015
100/100
15%
Value7.9 s
43/100
10%
195 ms
236 ms
146 ms
159 ms
154 ms
Our browser made a total of 126 requests to load all elements on the main page. We found that 84% of them (106 requests) were addressed to the original Kew.org, 3% (4 requests) were made to Assets.kew.org and 3% (4 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (632 ms) belongs to the original domain Kew.org.
Page size can be reduced by 1.2 MB (48%)
2.6 MB
1.3 MB
In fact, the total size of Kew.org main page is 2.6 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 1.2 MB which makes up the majority of the site volume.
Potential reduce by 132.1 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 132.1 kB or 86% of the original size.
Potential reduce by 95.6 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. Kew images are well optimized though.
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 69% of the original size.
Potential reduce by 673.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. Kew.org needs all CSS files to be minified and compressed as it can save up to 673.0 kB or 88% of the original size.
Number of requests can be reduced by 79 (66%)
120
41
The browser has sent 120 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kew. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 47 to 1 for CSS and as a result speed up the page load time.
kew.org
195 ms
www.kew.org
236 ms
system.base.css
146 ms
system.menus.theme.css
159 ms
system.messages.theme.css
154 ms
system.theme.css
157 ms
comment.theme.css
158 ms
date.css
159 ms
datepicker.1.7.css
220 ms
date_repeat_field.css
229 ms
field.theme.css
233 ms
google_cse.css
230 ms
kew_wysiwyg.css
233 ms
node.css
230 ms
search.theme.css
295 ms
user.theme.css
305 ms
user.base.css
305 ms
views.css
306 ms
ctools.css
307 ms
eu_cookie_compliance.css
308 ms
panels.css
370 ms
views_slideshow.css
379 ms
home.layout.css
379 ms
base_slider.css
380 ms
flexslider_img.css
381 ms
flexslider.css
382 ms
mobile_navigation.css
445 ms
footer.layout.css
454 ms
widgets.css
456 ms
font-awesome.css
456 ms
bootstrap.css
460 ms
base.css
466 ms
default.css
521 ms
compatibility.css
528 ms
superfish.css
530 ms
kew.normalize.css
530 ms
kew.hacks.css
533 ms
kew-custom.css
21 ms
kew.styles.css
550 ms
lowo.styles.css
461 ms
contextual.theme.css
459 ms
color.admin.css
458 ms
filter.theme.css
458 ms
forum.theme.css
459 ms
openid.theme.css
523 ms
jquery.simplyscroll.css
470 ms
site.layout.css
462 ms
jquery.min.js
537 ms
jquery.once.js
464 ms
drupal.js
463 ms
no-js.js
525 ms
google_cse.js
471 ms
esi.js
463 ms
jquery.esi.js
465 ms
panels.js
464 ms
views_slideshow.js
526 ms
jquery.flexslider-min.js
534 ms
mobile_menu.js
472 ms
mobile_navigation.js
465 ms
googleanalytics.js
465 ms
tb-megamenu-frontend.js
467 ms
tb-megamenu-touch.js
525 ms
kew.behaviors.js
534 ms
jquery.html5-placeholder-shim.js
471 ms
search_mobile.js
463 ms
visit_toggle.js
464 ms
respond.min.js
462 ms
font-awesome.css
516 ms
caption_align.js
544 ms
responsive-mobile.js
489 ms
cloud-zoom.1.0.3.js
483 ms
removeTooltip.js
483 ms
kew_map.js
482 ms
kew_custom.js
523 ms
jquery.simplyscroll.js
468 ms
eu_cookie_compliance.js
467 ms
flexslider.load.js
496 ms
analytics.js
20 ms
collect
12 ms
logoMobile_0.gif
36 ms
footer_logo.gif
36 ms
instagram32.gif
37 ms
logo_small_whitespaceleft.gif
131 ms
orchids%20kew%20site%201005x405.jpg
248 ms
FieldIDWithJT_homepageslider_web.jpg
348 ms
IMG_20160120_125543.jpg
406 ms
pirogues.jpg
132 ms
4%20combo%20A.jpg
632 ms
Tecophilaea%20cyanocrocus%204532-crop.jpg
231 ms
orchid-tea-towel-crop.jpg
170 ms
ALP_AM07KG20120430T152821.jpg
346 ms
KPPCONT_066521.jpg
344 ms
KewAutumn2014_186_kidsinPOW_750by405px.jpg
344 ms
WMAN_AM07KG20130821T132233-crop.jpg
403 ms
9781842466094-crop.jpg
405 ms
Jodrell_Wolfson_Wing_promo_220pxby146px.jpg
408 ms
facebook.png
409 ms
twitter.png
487 ms
youtube.png
487 ms
gtm.js
124 ms
eCnkv3hRMIY
181 ms
header_bar.gif
463 ms
button_bullet.png
462 ms
breadcrumb-home.png
463 ms
button_bullet_2nd.png
544 ms
footer_bar.gif
546 ms
facebook.png
548 ms
twitter.png
546 ms
youtube.png
549 ms
google_custom_search_watermark.gif
77 ms
L1_nav_bar.gif
524 ms
mb_search_icon.jpg
527 ms
left-arrow.gif
527 ms
right-arrow.gif
531 ms
collect
18 ms
collect
81 ms
ActivityServer.bs
34 ms
flexslider-icon.woff
491 ms
www-embed-player-vflZsBgOl.css
78 ms
www-embed-player.js
102 ms
google_custom_search_watermark.gif
58 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
13 ms
ad_status.js
72 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
98 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
108 ms
collect
30 ms
kew.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
kew.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
kew.org 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kew.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 Kew.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.
kew.org
Open Graph description is not detected on the main page of Kew. 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: