Tools & Wizards About Us
policat.org screenshot

Report Summary

  • 97

    Performance

    Renders faster than
    94% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

policat.org

PoliCAT - Multilingual Petitions

Page Load Speed

3.3 sec in total

First Response

306 ms

Resources Loaded

2.8 sec

Page Rendered

254 ms

policat.org screenshot

About Website

Welcome to policat.org homepage info - get ready to check PoliCAT best content for France right away, or after learning these important things about policat.org

Multilingual petition and e-action service

Visit policat.org

Key Findings

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

Performance Metrics

policat.org performance score

97

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

88/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

95/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value10 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.0 s

99/100

10%

Network Requests Diagram

policat.org

306 ms

www.policat.org

527 ms

frontend.css

202 ms

frontend.js

493 ms

policat_widget_outer.js

298 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 534.8 kB (21%)

Content Size

2.5 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Policat.org main page is 2.5 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. 25% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 14.6 kB

  • Original 18.8 kB
  • After minification 17.2 kB
  • After compression 4.3 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 14.6 kB or 77% of the original size.

Image Optimization

-14%

Potential reduce by 298.4 kB

  • Original 2.2 MB
  • After minification 1.9 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. Obviously, PoliCAT needs image optimization as it can save up to 298.4 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 143.5 kB

  • Original 220.3 kB
  • After minification 220.0 kB
  • After compression 76.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 143.5 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 78.3 kB

  • Original 94.5 kB
  • After minification 93.8 kB
  • After compression 16.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. Policat.org needs all CSS files to be minified and compressed as it can save up to 78.3 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

28

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 28 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PoliCAT. 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 JavaScripts and as a result speed up the page load time.

Network Requests Diagram

policat.org

policat.org

306 ms

www.policat.org

www.policat.org

527 ms

frontend.css

frontend.css

202 ms

frontend.js

frontend.js

493 ms

policat_widget_outer.js

policat_widget_outer.js

298 ms

dashboard_home.js

dashboard_home.js

298 ms

portal_logo.png

portal_logo.png

102 ms

icon_rss.png

icon_rss.png

120 ms

64a6ed576c3ce0793d19cc6d56b2af79970d0a88.png

64a6ed576c3ce0793d19cc6d56b2af79970d0a88.png

799 ms

d24367b1c7a78707ba1cf52eb240203e400d6deb.png

d24367b1c7a78707ba1cf52eb240203e400d6deb.png

817 ms

5823ba441bcb4efbfbd597ed876abad1b4579c95.png

5823ba441bcb4efbfbd597ed876abad1b4579c95.png

601 ms

5566421a1a1603a29ee649c0f641474eb1cce0a5.png

5566421a1a1603a29ee649c0f641474eb1cce0a5.png

218 ms

52a06230fbbb6df720b652bd0af08f99475cc7b9.jpg

52a06230fbbb6df720b652bd0af08f99475cc7b9.jpg

1100 ms

318559ee164b77f155f3fa7f9269ad1780c71304.jpg

318559ee164b77f155f3fa7f9269ad1780c71304.jpg

675 ms

7bb3d27617a02c33ee094b25522a786fa650239a.png

7bb3d27617a02c33ee094b25522a786fa650239a.png

319 ms

d6d4798b703771c5e146943d145fb286ddcd4626.png

d6d4798b703771c5e146943d145fb286ddcd4626.png

517 ms

86b43c3380c5c7549b42245e3dbdf61c6e7d1651.png

86b43c3380c5c7549b42245e3dbdf61c6e7d1651.png

714 ms

6dda4e066f46d428ba273a62400500a24aaf1c74.png

6dda4e066f46d428ba273a62400500a24aaf1c74.png

701 ms

82b6f93fca54e5a977171131ca487e4bff35ca03.png

82b6f93fca54e5a977171131ca487e4bff35ca03.png

871 ms

72f947730a81214732a4bff31a0ed039

72f947730a81214732a4bff31a0ed039

802 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

103 ms

OpenSans.css

OpenSans.css

101 ms

Title_en.png

Title_en.png

105 ms

policat.spr.png

policat.spr.png

208 ms

3195ea43d5e81ba0ebab756e1b74f615c481d3f8.png

3195ea43d5e81ba0ebab756e1b74f615c481d3f8.png

101 ms

facebook-32.png

facebook-32.png

102 ms

twitter-32.png

twitter-32.png

99 ms

googleplus-32.png

googleplus-32.png

99 ms

email-32.png

email-32.png

195 ms

OpenSans-Regular.woff

OpenSans-Regular.woff

205 ms

OpenSans-Bold.woff

OpenSans-Bold.woff

198 ms

frontend_print.css

frontend_print.css

103 ms

Accessibility Review

policat.org accessibility score

93

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 progressbar elements do not have accessible names.

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.

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

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

Best Practices

policat.org best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

policat.org SEO score

92

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

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Policat.org 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 Policat.org main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

policat.org

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