Report Summary

  • 91

    Performance

    Renders faster than
    91% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 50

    SEO

    Google-friendlier than
    18% of websites

Page Load Speed

1.8 sec in total

First Response

307 ms

Resources Loaded

1.3 sec

Page Rendered

142 ms

About Website

Visit doc.spip.org now to see the best up-to-date Doc Spip content for France and also check out these interesting facts you probably never knew about doc.spip.org

Visit doc.spip.org

Key Findings

We analyzed Doc.spip.org page load time and found that the first response time was 307 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

doc.spip.org performance score

91

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value2.7 s

85/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.07

96/100

15%

TTI (Time to Interactive)

Value2.7 s

97/100

10%

Network Requests Diagram

doc.spip.org

307 ms

code.spip.net

371 ms

css2

29 ms

css2

46 ms

variables.css

91 ms

Our browser made a total of 8 requests to load all elements on the main page. We found that 13% of them (1 request) were addressed to the original Doc.spip.org, 50% (4 requests) were made to Code.spip.net and 25% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (447 ms) relates to the external source Spip.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 26.5 kB (47%)

Content Size

55.8 kB

After Optimization

29.4 kB

In fact, the total size of Doc.spip.org main page is 55.8 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. Only 10% of websites need less resources to load. HTML takes 29.3 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 25.7 kB

  • Original 29.3 kB
  • After minification 21.9 kB
  • After compression 3.5 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. This page needs HTML code to be minified as it can gain 7.4 kB, which is 25% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 25.7 kB or 88% of the original size.

Image Optimization

-2%

Potential reduce by 412 B

  • Original 24.0 kB
  • After minification 23.6 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. Doc Spip images are well optimized though.

CSS Optimization

-12%

Potential reduce by 317 B

  • Original 2.6 kB
  • After minification 2.6 kB
  • After compression 2.2 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. Doc.spip.org needs all CSS files to be minified and compressed as it can save up to 317 B or 12% of the original size.

Requests Breakdown

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

Requests Now

6

After Optimization

3

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Doc Spip. 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.

Accessibility Review

doc.spip.org accessibility score

71

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 have valid values

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

Document doesn't have a <title> element

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Best Practices

doc.spip.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

SEO Factors

doc.spip.org SEO score

50

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

Document doesn't have a <title> element

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Doc.spip.org can be misinterpreted by Google and other search engines. Our service has detected that French 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 Doc.spip.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 description is not detected on the main page of Doc Spip. 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: