Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 77

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

ipbes.net

IPBES Home page | IPBES secretariat

Page Load Speed

1.1 sec in total

First Response

93 ms

Resources Loaded

707 ms

Page Rendered

310 ms

ipbes.net screenshot

About Website

Click here to check amazing IPBES content for United States. Otherwise, check out these important facts you probably never knew about ipbes.net

The Intergovernmental Science-Policy Platform on Biodiversity and Ecosystem Services (IPBES) is the intergovernmental body which assesses the state of biodiversity and of the ecosystem services.

Visit ipbes.net

Key Findings

We analyzed Ipbes.net page load time and found that the first response time was 93 ms and then it took 1 sec 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

ipbes.net performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value27.9 s

0/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value780 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value1.876

0/100

15%

TTI (Time to Interactive)

Value24.4 s

1/100

10%

Network Requests Diagram

ipbes.net

93 ms

www.ipbes.net

198 ms

css

95 ms

css_lQaZfjVpwP_oGNqdtWCSpJT1EMqXdMiU84ekLLxQnc4.css

59 ms

css_C9JovfmRv1Llq3HKz-i_pwhfF3DXq0tpSdWArSB6Zsw.css

65 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 91% of them (51 requests) were addressed to the original Ipbes.net, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (202 ms) belongs to the original domain Ipbes.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 577.2 kB (31%)

Content Size

1.9 MB

After Optimization

1.3 MB

In fact, the total size of Ipbes.net main page is 1.9 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. 65% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 95.4 kB

  • Original 117.8 kB
  • After minification 113.6 kB
  • After compression 22.4 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 95.4 kB or 81% of the original size.

Image Optimization

-3%

Potential reduce by 39.2 kB

  • Original 1.2 MB
  • After minification 1.1 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. IPBES images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 203.2 kB

  • Original 291.9 kB
  • After minification 240.1 kB
  • After compression 88.8 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 203.2 kB or 70% of the original size.

CSS Optimization

-82%

Potential reduce by 239.4 kB

  • Original 292.3 kB
  • After minification 286.8 kB
  • After compression 52.9 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. Ipbes.net needs all CSS files to be minified and compressed as it can save up to 239.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (51%)

Requests Now

53

After Optimization

26

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

Accessibility Review

ipbes.net accessibility score

79

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.

Best Practices

ipbes.net best practices score

77

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

Missing source maps for large first-party JavaScript

SEO Factors

ipbes.net SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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 Ipbes.net 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 Ipbes.net 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 description is not detected on the main page of IPBES. 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: