Tools & Wizards About Us
stthomasbotanicalgarden.com screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 40

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

stthomasbotanicalgarden.com

St. Thomas Botanical Garden, virgin islands eco-attraction, orchids, bromeliads, virgin islands garden

Page Load Speed

1 sec in total

First Response

37 ms

Resources Loaded

892 ms

Page Rendered

107 ms

stthomasbotanicalgarden.com screenshot

About Website

Click here to check amazing St Thomas Botanical Garden content. Otherwise, check out these important facts you probably never knew about stthomasbotanicalgarden.com

St. Thomas's newest botanical garden and eco-attraction feauring over 1000 orchids in a tropical botanical setting. Bromeliads, heliconas and many other tropical plants with interpretive signage also ...

Visit stthomasbotanicalgarden.com

Key Findings

We analyzed Stthomasbotanicalgarden.com page load time and found that the first response time was 37 ms and then it took 999 ms 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.

Performance Metrics

stthomasbotanicalgarden.com performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value1,720 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.083

94/100

15%

TTI (Time to Interactive)

Value23.4 s

1/100

10%

Network Requests Diagram

www.stthomasbotanicalgarden.com

37 ms

site.css

11 ms

duel.js

24 ms

jq.js

562 ms

analytics.js

55 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Stthomasbotanicalgarden.com, 30% (17 requests) were made to Nebula.wsimg.com and 21% (12 requests) were made to P3pprd001.cloudstorage.secureserver.net. The less responsive or slowest element that took the longest time to load (785 ms) relates to the external source Nebula.wsimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 341.8 kB (41%)

Content Size

843.8 kB

After Optimization

502.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Stthomasbotanicalgarden.com main page is 843.8 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. 40% of websites need less resources to load. Javascripts take 513.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 63.4 kB

  • Original 76.0 kB
  • After minification 76.0 kB
  • After compression 12.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 63.4 kB or 83% of the original size.

Image Optimization

-18%

Potential reduce by 33.0 kB

  • Original 179.3 kB
  • After minification 146.3 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. Obviously, St Thomas Botanical Garden needs image optimization as it can save up to 33.0 kB or 18% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-48%

Potential reduce by 245.4 kB

  • Original 513.0 kB
  • After minification 512.4 kB
  • After compression 267.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 245.4 kB or 48% of the original size.

CSS Optimization

-0%

Potential reduce by 46 B

  • Original 75.4 kB
  • After minification 75.4 kB
  • After compression 75.4 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. Stthomasbotanicalgarden.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 29 (54%)

Requests Now

54

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of St Thomas Botanical Garden. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.stthomasbotanicalgarden.com

www.stthomasbotanicalgarden.com

37 ms

site.css

site.css

11 ms

duel.js

duel.js

24 ms

jq.js

jq.js

562 ms

analytics.js

analytics.js

55 ms

a36b6de6535372d88d86429d3dc222eb

a36b6de6535372d88d86429d3dc222eb

157 ms

150_logo-11900-2.png

150_logo-11900-2.png

85 ms

258d22d4a8ee476ff65e6be6377a91c5

258d22d4a8ee476ff65e6be6377a91c5

53 ms

1b25e5fb43471834b0a153c8645e0bf9

1b25e5fb43471834b0a153c8645e0bf9

53 ms

458d5a3682273b6f2c4a92bd2236a662

458d5a3682273b6f2c4a92bd2236a662

52 ms

7b77e9f781bfe8a3055dc248fae3407b

7b77e9f781bfe8a3055dc248fae3407b

557 ms

335604f0a12be9907a4cab2c50a2e35f

335604f0a12be9907a4cab2c50a2e35f

556 ms

ad696cf38eb32a7e178380a4b976c20e

ad696cf38eb32a7e178380a4b976c20e

556 ms

b461bb4fa755fbad48bf43690f785333

b461bb4fa755fbad48bf43690f785333

557 ms

1d53300f11dd0e39351c412a222d7399

1d53300f11dd0e39351c412a222d7399

557 ms

8748e27dec46bac5cef41dd42e93c6a8

8748e27dec46bac5cef41dd42e93c6a8

158 ms

fd4a79d7e1b069afa02b168e3812d3d1

fd4a79d7e1b069afa02b168e3812d3d1

530 ms

be1511d4f773de6b553c1358380ab7e9

be1511d4f773de6b553c1358380ab7e9

557 ms

6e5693fca6590a2371d7ce926ef71722

6e5693fca6590a2371d7ce926ef71722

784 ms

91e89b7a814581e356d98d99029f190c

91e89b7a814581e356d98d99029f190c

782 ms

51cebd12cf55c76f6694c555df3b872e

51cebd12cf55c76f6694c555df3b872e

583 ms

b99469ec257c5449a80c0aeba31e8cd4

b99469ec257c5449a80c0aeba31e8cd4

583 ms

b59552e2c6cc0a56fee14961ed5478ce

b59552e2c6cc0a56fee14961ed5478ce

785 ms

CoE2017_WidgetAsset-14348-2.png

CoE2017_WidgetAsset-14348-2.png

96 ms

scc-c2.min.js

scc-c2.min.js

42 ms

wejs

wejs

104 ms

wejs

wejs

70 ms

collect

collect

13 ms

js

js

64 ms

WidgetEmbed-selfserveprop

WidgetEmbed-selfserveprop

50 ms

yxKuinmBIXM

yxKuinmBIXM

112 ms

WidgetEmbed-certificateOfExcellence

WidgetEmbed-certificateOfExcellence

43 ms

facebookSDKHelper.js

facebookSDKHelper.js

455 ms

media.gallery.js

media.gallery.js

543 ms

cookiemanager.js

cookiemanager.js

538 ms

iebackground.js

iebackground.js

539 ms

t4b_widget_coe-v2381509749a.css

t4b_widget_coe-v2381509749a.css

25 ms

cdswidgets_min-c-v2395114504a.js

cdswidgets_min-c-v2395114504a.js

27 ms

t4b_widget_self_serve_property-v24221562771a.css

t4b_widget_self_serve_property-v24221562771a.css

23 ms

cdswidgets_m-c-v22480917520a.js

cdswidgets_m-c-v22480917520a.js

27 ms

www-player.css

www-player.css

6 ms

www-embed-player.js

www-embed-player.js

40 ms

base.js

base.js

63 ms

ad_status.js

ad_status.js

165 ms

om_QuI9M6WDewyV11PDqwyZXtjss-zYzBgeHLXyLCgE.js

om_QuI9M6WDewyV11PDqwyZXtjss-zYzBgeHLXyLCgE.js

107 ms

embed.js

embed.js

43 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

46 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

49 ms

util.fbSDKLoader.js

util.fbSDKLoader.js

89 ms

util.window.js

util.window.js

88 ms

Create

Create

103 ms

id

id

11 ms

util.instances.js

util.instances.js

98 ms

util.model.js

util.model.js

98 ms

documentHelper.js

documentHelper.js

96 ms

helper.js

helper.js

96 ms

growl.js

growl.js

96 ms

Accessibility Review

stthomasbotanicalgarden.com accessibility score

40

Accessibility Issues

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

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

High

Definition list items are not wrapped in <dl> elements

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

stthomasbotanicalgarden.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

stthomasbotanicalgarden.com SEO score

91

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stthomasbotanicalgarden.com 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 Stthomasbotanicalgarden.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.

Social Sharing Optimization

stthomasbotanicalgarden.com

Open Graph data is detected on the main page of St Thomas Botanical Garden. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: