Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

futureprimitive.org

Future Primitive Podcasts - Protecting the Living Earth

Page Load Speed

4.3 sec in total

First Response

702 ms

Resources Loaded

2.3 sec

Page Rendered

1.3 sec

futureprimitive.org screenshot

About Website

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

For over 16 years, Future Primitive has been hosting intimate conversations with authors, visionaries and innovators who speak about our connection and partnership with the Living Earth.

Visit futureprimitive.org

Key Findings

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

Performance Metrics

futureprimitive.org performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.3 s

7/100

10%

LCP (Largest Contentful Paint)

Value18.6 s

0/100

25%

SI (Speed Index)

Value13.0 s

2/100

10%

TBT (Total Blocking Time)

Value3,300 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.079

94/100

15%

TTI (Time to Interactive)

Value19.2 s

2/100

10%

Network Requests Diagram

www.futureprimitive.org

702 ms

global.css

111 ms

iepngfix_tilebg.js

83 ms

global.js

87 ms

style.css

88 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 68% of them (49 requests) were addressed to the original Futureprimitive.org, 21% (15 requests) were made to Apis.google.com and 3% (2 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (702 ms) belongs to the original domain Futureprimitive.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 781.6 kB (49%)

Content Size

1.6 MB

After Optimization

813.0 kB

In fact, the total size of Futureprimitive.org main page is 1.6 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. 60% of websites need less resources to load. Javascripts take 693.3 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 266.9 kB

  • Original 366.8 kB
  • After minification 364.3 kB
  • After compression 99.9 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 266.9 kB or 73% of the original size.

Image Optimization

-2%

Potential reduce by 7.7 kB

  • Original 469.4 kB
  • After minification 461.8 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. Future Primitive images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 453.2 kB

  • Original 693.3 kB
  • After minification 672.6 kB
  • After compression 240.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 453.2 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 53.8 kB

  • Original 65.0 kB
  • After minification 52.2 kB
  • After compression 11.1 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. Futureprimitive.org needs all CSS files to be minified and compressed as it can save up to 53.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 33 (47%)

Requests Now

70

After Optimization

37

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

Accessibility Review

futureprimitive.org accessibility score

73

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

[aria-*] attributes do not match their roles

High

ARIA IDs are not unique

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

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

futureprimitive.org best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

futureprimitive.org 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

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 Futureprimitive.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 Futureprimitive.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 Future Primitive. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: