Tools & Wizards About Us
docs.perfsonar.net screenshot

Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 68

    SEO

    Google-friendlier than
    28% of websites

docs.perfsonar.net

User Guide for perfSONAR 5.0.8 — perfSONAR Toolkit 5.0.8 documentation

Page Load Speed

1.1 sec in total

First Response

108 ms

Resources Loaded

306 ms

Page Rendered

636 ms

docs.perfsonar.net screenshot

About Website

Click here to check amazing Docs PerfSONAR content for Cuba. Otherwise, check out these important facts you probably never knew about docs.perfsonar.net

Visit docs.perfsonar.net

Key Findings

We analyzed Docs.perfsonar.net page load time and found that the first response time was 108 ms and then it took 942 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

docs.perfsonar.net performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

88/100

10%

LCP (Largest Contentful Paint)

Value1.9 s

98/100

25%

SI (Speed Index)

Value1.9 s

100/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.076

95/100

15%

TTI (Time to Interactive)

Value1.9 s

100/100

10%

Network Requests Diagram

docs.perfsonar.net

108 ms

default.css

41 ms

pygments.css

56 ms

perfsonar.css

57 ms

jquery.js

80 ms

Our browser made a total of 13 requests to load all elements on the main page. We found that all of those requests were addressed to Docs.perfsonar.net and no external sources were called. The less responsive or slowest element that took the longest time to load (108 ms) belongs to the original domain Docs.perfsonar.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 55.4 kB (70%)

Content Size

78.7 kB

After Optimization

23.3 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Docs.perfsonar.net main page is 78.7 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. 15% of websites need less resources to load. HTML takes 41.9 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 35.4 kB

  • Original 41.9 kB
  • After minification 40.4 kB
  • After compression 6.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 35.4 kB or 85% of the original size.

Image Optimization

-17%

Potential reduce by 2.6 kB

  • Original 15.4 kB
  • After minification 12.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. Obviously, Docs PerfSONAR needs image optimization as it can save up to 2.6 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

CSS Optimization

-81%

Potential reduce by 17.4 kB

  • Original 21.5 kB
  • After minification 13.8 kB
  • After compression 4.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. Docs.perfsonar.net needs all CSS files to be minified and compressed as it can save up to 17.4 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (25%)

Requests Now

12

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

docs.perfsonar.net

docs.perfsonar.net

108 ms

default.css

default.css

41 ms

pygments.css

pygments.css

56 ms

perfsonar.css

perfsonar.css

57 ms

jquery.js

jquery.js

80 ms

underscore.js

underscore.js

57 ms

doctools.js

doctools.js

58 ms

basic.css

basic.css

40 ms

perfSONAR-header.gif

perfSONAR-header.gif

40 ms

ESnet-ps.png

ESnet-ps.png

36 ms

geant-ps.png

geant-ps.png

39 ms

IU-ps.png

IU-ps.png

40 ms

I2-ps.png

I2-ps.png

36 ms

Accessibility Review

docs.perfsonar.net accessibility score

84

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

docs.perfsonar.net 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

SEO Factors

docs.perfsonar.net SEO score

68

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    N/A

  • Encoding

    UTF-8

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

docs.perfsonar.net

Open Graph description is not detected on the main page of Docs PerfSONAR. 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: