23.5 sec in total
11.3 sec
12.1 sec
104 ms
Visit stri.org now to see the best up-to-date Stri content and also check out these interesting facts you probably never knew about stri.org
The Smithsonian Tropical Research Institute was founded with the purpose of increasing and sharing knowledge about the past, present and future of tropical ecosystems and their relevance to human welf...
Visit stri.orgWe analyzed Stri.org page load time and found that the first response time was 11.3 sec and then it took 12.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
stri.org performance score
name
value
score
weighting
Value12.6 s
0/100
10%
Value19.3 s
0/100
25%
Value13.2 s
2/100
10%
Value310 ms
77/100
30%
Value0.031
100/100
15%
Value15.2 s
7/100
10%
11317 ms
12 ms
29 ms
37 ms
30 ms
Our browser made a total of 104 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Stri.org, 6% (6 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to . The less responsive or slowest element that took the longest time to load (11.3 sec) relates to the external source Stri.si.edu.
Page size can be reduced by 367.8 kB (17%)
2.2 MB
1.8 MB
In fact, the total size of Stri.org main page is 2.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. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 56.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 56.1 kB or 81% of the original size.
Potential reduce by 14.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. Stri images are well optimized though.
Potential reduce by 59.3 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 59.3 kB or 38% of the original size.
Potential reduce by 237.5 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. Stri.org needs all CSS files to be minified and compressed as it can save up to 237.5 kB or 35% of the original size.
Number of requests can be reduced by 82 (88%)
93
11
The browser has sent 93 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Stri. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
stri.si.edu
11317 ms
system.base.css
12 ms
system.messages.css
29 ms
system.theme.css
37 ms
slick.css
30 ms
jquery.ui.button.min.css
30 ms
jquery.ui.resizable.min.css
28 ms
jquery.ui.dialog.min.css
28 ms
ldap_user.css
35 ms
date.css
38 ms
field.css
35 ms
node.css
36 ms
search.css
35 ms
user.css
43 ms
youtube.css
41 ms
views.css
42 ms
colorbox_style.css
39 ms
ctools.css
43 ms
panels.css
41 ms
bootstrap_panels_horizontal_tabs.css
44 ms
locale.css
44 ms
css
97 ms
superfish.css
46 ms
bootstrap.css
52 ms
stri.style.css
65 ms
stri.custom.css
46 ms
STRI.css
98 ms
slidebars.min.css
50 ms
modernizr.js
64 ms
jquery.min.js
95 ms
jquery-extend-3.4.0.js
93 ms
jquery-html-prefilter-3.5.0-backport.js
92 ms
jquery.once.js
94 ms
drupal.js
101 ms
stri-lazy-fix.js
95 ms
bootstrap.min.js
44 ms
jquery.ui.core.min.js
101 ms
jquery.ui.widget.min.js
101 ms
js
107 ms
element.js
101 ms
slick.min.js
100 ms
jquery.ui.button.min.js
97 ms
jquery.ui.mouse.min.js
82 ms
jquery.ui.draggable.min.js
80 ms
jquery.ui.position.min.js
81 ms
jquery.ui.position-1.13.0-backport.js
81 ms
jquery.ui.resizable.min.js
82 ms
jquery.ui.dialog.min.js
76 ms
jquery.ui.dialog-1.13.0-backport.js
77 ms
media_colorbox.js
75 ms
spamspan.js
76 ms
stri.overrides.js
76 ms
jquery.colorbox-min.js
78 ms
colorbox.js
73 ms
colorbox_style.js
75 ms
colorbox_load.js
72 ms
colorbox_inline.js
72 ms
stri-global-fpp.js
73 ms
slick.load.min.js
72 ms
bootstrap_panels_horizontal_tabs.js
72 ms
googleanalytics.js
72 ms
jquery.hoverIntent.minified.js
70 ms
supposition.js
69 ms
superfish.js
64 ms
supersubs.js
53 ms
superfish.js
25 ms
radix.script.js
25 ms
stri.script.js
24 ms
slidebars.min.js
25 ms
responsive-menu.js
24 ms
webtrends.js
23 ms
stri.print.css
8 ms
logo_stri.svg
80 ms
i-arrow--next__alt.svg
53 ms
i-arrow--up__alt.svg
51 ms
home-menu1-research.png
55 ms
i-facebook__white.svg
54 ms
i-twitter__white.svg
52 ms
i-instagram__white.svg
53 ms
i-youtube__white.svg
55 ms
dropdown-arrow.svg
57 ms
wtid.js
138 ms
ga6iaw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTa32J4wsL2JAlAhZqFCTx8cM.woff
35 ms
ga6iaw1J5X9T9RW6j9bNVls-hfgvz8JcMofYTa32J4wsL2JAlAhZT1eTx8cM.woff
45 ms
9pOvoAWrEAuw==
7 ms
E2wGb
6 ms
atz7Af0vAgw=
4 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyD9A-9a6VQ.woff
41 ms
o-0mIpQlx3QUlC5A4PNB6Ryti20_6n1iPHjcz6L1SoM-jCpoiyAaBO9a6VQ.woff
42 ms
fontawesome-webfont.woff
40 ms
ga6saw1J5X9T9RW6j9bNfFIMZhhWnFTyNZIQD1-_FXP0RgnaOg9MYBNLg_cIrq0.woff
40 ms
ga6saw1J5X9T9RW6j9bNfFIMZhhWnFTyNZIQD1-_FXP0RgnaOg9MYBOshPcIrq0.woff
41 ms
gateway.min.js
111 ms
early_bird_homepage_cover.jpg
118 ms
measuring_mangroves_cover.jpg
33 ms
april_special_events_cover.jpg
22 ms
i-search__white.svg
8 ms
i-pause.svg
17 ms
i-play__white.svg
19 ms
i-slider--prev.svg
27 ms
i-slider--next.svg
27 ms
dcs.gif
25 ms
fs.utils.js
8 ms
fs.compress.js
11 ms
stri.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 input fields do not have accessible names
[role]s are not contained by their required parent element
[role] values are not valid
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
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.
stri.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
stri.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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stri.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 Stri.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.
stri.org
Open Graph description is not detected on the main page of Stri. 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: