Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    25% of websites

demo.piwik.org

Demo Site - Web Analytics Reports - Matomo

Page Load Speed

3.1 sec in total

First Response

347 ms

Resources Loaded

2.6 sec

Page Rendered

91 ms

demo.piwik.org screenshot

About Website

Visit demo.piwik.org now to see the best up-to-date Demo Piwik content for United States and also check out these interesting facts you probably never knew about demo.piwik.org

Web Analytics report for Demo Site - Matomo

Visit demo.piwik.org

Key Findings

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

Performance Metrics

demo.piwik.org performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value11.9 s

4/100

10%

TBT (Total Blocking Time)

Value4,350 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.393

26/100

15%

TTI (Time to Interactive)

Value14.7 s

8/100

10%

Network Requests Diagram

index.php

347 ms

index.php

333 ms

index.php

715 ms

index.php

327 ms

bootstrap.css

83 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 114.7 kB (78%)

Content Size

146.9 kB

After Optimization

32.2 kB

In fact, the total size of Demo.piwik.org main page is 146.9 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. 25% of websites need less resources to load. HTML takes 117.1 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 96.3 kB

  • Original 117.1 kB
  • After minification 95.9 kB
  • After compression 20.7 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 21.2 kB, which is 18% 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 96.3 kB or 82% of the original size.

Image Optimization

-13%

Potential reduce by 1.1 kB

  • Original 8.6 kB
  • After minification 7.4 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, Demo Piwik needs image optimization as it can save up to 1.1 kB or 13% 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.3 kB

  • Original 21.3 kB
  • After minification 16.5 kB
  • After compression 4.0 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. Demo.piwik.org needs all CSS files to be minified and compressed as it can save up to 17.3 kB or 81% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

20

After Optimization

20

The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Demo Piwik. According to our analytics all requests are already optimized.

Accessibility Review

demo.piwik.org accessibility score

77

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

[role]s are not contained by their required parent element

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

[id] attributes on active, focusable elements are not unique

High

Some elements have a [tabindex] value greater than 0

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

demo.piwik.org best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

demo.piwik.org SEO score

67

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

High

Image elements do not have [alt] attributes

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

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 Demo.piwik.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 Demo.piwik.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 Demo Piwik. 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: