Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 81% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

tbep.org

Tampa Bay Estuary Program - A Catalyst for Restoration

Page Load Speed

9.3 sec in total

First Response

217 ms

Resources Loaded

8.5 sec

Page Rendered

551 ms

tbep.org screenshot

About Website

Click here to check amazing Tbep content for United States. Otherwise, check out these important facts you probably never knew about tbep.org

The Tampa Bay Estuary Program is 1 of 28 National Estuary Programs designated by Congress to restore & protect “estuaries of national significance.

Visit tbep.org

Key Findings

We analyzed Tbep.org page load time and found that the first response time was 217 ms and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

tbep.org performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value26.2 s

0/100

25%

SI (Speed Index)

Value46.7 s

0/100

10%

TBT (Total Blocking Time)

Value61,010 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.21

59/100

15%

TTI (Time to Interactive)

Value81.7 s

0/100

10%

Network Requests Diagram

tbep.org

217 ms

nox8qgN6X0XCZEhMkxekbQEA6dI.js

301 ms

select2.min.css

169 ms

iconfonts.css

170 ms

frontend.min.css

247 ms

Our browser made a total of 179 requests to load all elements on the main page. We found that 46% of them (82 requests) were addressed to the original Tbep.org, 7% (13 requests) were made to Youtube.com and 4% (8 requests) were made to C1.adform.net. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain Tbep.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 978.1 kB (10%)

Content Size

9.5 MB

After Optimization

8.5 MB

In fact, the total size of Tbep.org main page is 9.5 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. Only a small number of websites need less resources to load. Images take 8.3 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 193.8 kB

  • Original 234.5 kB
  • After minification 232.1 kB
  • After compression 40.8 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 193.8 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 366.6 kB

  • Original 8.3 MB
  • After minification 7.9 MB

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. Tbep images are well optimized though.

JavaScript Optimization

-24%

Potential reduce by 91.9 kB

  • Original 384.1 kB
  • After minification 383.8 kB
  • After compression 292.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 91.9 kB or 24% of the original size.

CSS Optimization

-54%

Potential reduce by 325.8 kB

  • Original 603.6 kB
  • After minification 601.1 kB
  • After compression 277.7 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. Tbep.org needs all CSS files to be minified and compressed as it can save up to 325.8 kB or 54% of the original size.

Requests Breakdown

Number of requests can be reduced by 127 (79%)

Requests Now

160

After Optimization

33

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

Accessibility Review

tbep.org accessibility score

93

Accessibility Issues

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

High

button, link, and menuitem elements do not have accessible names.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Links do not have a discernible name

Best Practices

tbep.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

tbep.org SEO score

90

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

Links do not have descriptive text

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 Tbep.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 Tbep.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.

Social Sharing Optimization

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