Report Summary

  • 27

    Performance

    Renders faster than
    47% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

saveourseas.com

Home - Save Our Seas Foundation

Page Load Speed

3.2 sec in total

First Response

688 ms

Resources Loaded

1.9 sec

Page Rendered

662 ms

saveourseas.com screenshot

About Website

Click here to check amazing Save Our Seas content for United States. Otherwise, check out these important facts you probably never knew about saveourseas.com

The Save Our Seas Foundation works to protect our oceans by funding research, conservation and education projects focusing primarily on charismatic marine megafauna.

Visit saveourseas.com

Key Findings

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

Performance Metrics

saveourseas.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value12.5 s

3/100

10%

TBT (Total Blocking Time)

Value710 ms

41/100

30%

CLS (Cumulative Layout Shift)

Value0.217

57/100

15%

TTI (Time to Interactive)

Value18.0 s

3/100

10%

Network Requests Diagram

saveourseas.com

688 ms

styles-desktop.css

487 ms

styles.css

7 ms

wp-geo.css

7 ms

jquery.js

14 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 90% of them (47 requests) were addressed to the original Saveourseas.com, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (688 ms) belongs to the original domain Saveourseas.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 641.9 kB (32%)

Content Size

2.0 MB

After Optimization

1.4 MB

In fact, the total size of Saveourseas.com main page is 2.0 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.

HTML Optimization

-71%

Potential reduce by 22.6 kB

  • Original 31.7 kB
  • After minification 31.6 kB
  • After compression 9.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.6 kB or 71% of the original size.

Image Optimization

-8%

Potential reduce by 107.0 kB

  • Original 1.3 MB
  • After minification 1.2 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. Save Our Seas images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 415.6 kB

  • Original 595.5 kB
  • After minification 595.4 kB
  • After compression 179.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 415.6 kB or 70% of the original size.

CSS Optimization

-86%

Potential reduce by 96.7 kB

  • Original 112.4 kB
  • After minification 110.8 kB
  • After compression 15.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. Saveourseas.com needs all CSS files to be minified and compressed as it can save up to 96.7 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (22%)

Requests Now

49

After Optimization

38

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

Accessibility Review

saveourseas.com accessibility score

86

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.

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

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

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

SEO Factors

saveourseas.com SEO score

79

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Saveourseas.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Saveourseas.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

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