1.4 sec in total
286 ms
873 ms
203 ms
Welcome to ntbg.org homepage info - get ready to check Ntbg best content for United States right away, or after learning these important things about ntbg.org
The National Tropical Botanical garden is dedicated to preserving tropical plant diversity and stemming the tide of extinction - through plant exploration, ...
Visit ntbg.orgWe analyzed Ntbg.org page load time and found that the first response time was 286 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
ntbg.org performance score
name
value
score
weighting
Value5.3 s
7/100
10%
Value15.6 s
0/100
25%
Value10.8 s
6/100
10%
Value2,930 ms
3/100
30%
Value0.085
93/100
15%
Value28.1 s
0/100
10%
286 ms
63 ms
88 ms
67 ms
58 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 78% of them (40 requests) were addressed to the original Ntbg.org, 8% (4 requests) were made to Translate.googleapis.com and 6% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (338 ms) belongs to the original domain Ntbg.org.
Page size can be reduced by 74.9 kB (18%)
421.1 kB
346.2 kB
In fact, the total size of Ntbg.org main page is 421.1 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. 20% of websites need less resources to load. Images take 235.4 kB which makes up the majority of the site volume.
Potential reduce by 22.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 22.1 kB or 77% of the original size.
Potential reduce by 6.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. Ntbg images are well optimized though.
Potential reduce by 38.9 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 38.9 kB or 27% of the original size.
Potential reduce by 7.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. Ntbg.org needs all CSS files to be minified and compressed as it can save up to 7.3 kB or 57% of the original size.
Number of requests can be reduced by 28 (56%)
50
22
The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ntbg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
ntbg.org
286 ms
styles.css
63 ms
styleswitcher.js
88 ms
menu.js
67 ms
element.js
58 ms
large.css
35 ms
medium.css
35 ms
small.css
35 ms
x-small.css
34 ms
translateelement.css
55 ms
main.js
65 ms
bg.jpg
36 ms
header.jpg
34 ms
spacer.gif
38 ms
menu_separator.gif
35 ms
search.gif
91 ms
menu_left.jpg
68 ms
menu_about.jpg
70 ms
menu_institutes.jpg
69 ms
menu_gardens.jpg
92 ms
menu_collections.jpg
72 ms
menu_plants.jpg
102 ms
menu_help.jpg
103 ms
menu_sharing.jpg
102 ms
home34.jpg
219 ms
shim.gif
134 ms
shdw.gif
135 ms
shdw_top.gif
134 ms
home_text_bg.gif
135 ms
gobotanical.jpg
171 ms
ad_lego.jpg
163 ms
ad_savetheday.gif
338 ms
ad_funrun.jpg
263 ms
ad_artshow.jpg
169 ms
social_facebook.gif
197 ms
social_twitter.gif
201 ms
fadeline.gif
201 ms
arrow_rt.gif
234 ms
shdw_r.gif
234 ms
shdw_r_top.gif
235 ms
footer_bg.jpg
251 ms
footer_shadow_bg.gif
266 ms
analytics.js
20 ms
element_main.js
42 ms
linkid.js
11 ms
collect
35 ms
collect
65 ms
translate_24dp.png
63 ms
l
40 ms
googlelogo_color_42x16dp.png
68 ms
xx-small.css
34 ms
ntbg.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.
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
Links do not have a discernible name
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
ntbg.org 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
ntbg.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
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
Tap targets are not sized appropriately
EN
EN
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ntbg.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 Ntbg.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
ntbg.org
Open Graph description is not detected on the main page of Ntbg. 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: