Tools & Wizards About Us
apur.org screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

apur.org

Apur - Atelier parisien d'urbanisme - Urbanisme Paris et Métropole du Grand Paris

Page Load Speed

2.5 sec in total

First Response

248 ms

Resources Loaded

2 sec

Page Rendered

191 ms

apur.org screenshot

About Website

Click here to check amazing Apur content for France. Otherwise, check out these important facts you probably never knew about apur.org

L’Apur a pour missions de documenter, analyser et développer des stratégies prospectives concernant les évolutions urbaines et sociétales à Paris et dans la Métropole du Grand Paris.

Visit apur.org

Key Findings

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

Performance Metrics

apur.org performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value15.6 s

0/100

25%

SI (Speed Index)

Value17.7 s

0/100

10%

TBT (Total Blocking Time)

Value23,990 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.263

47/100

15%

TTI (Time to Interactive)

Value33.8 s

0/100

10%

Network Requests Diagram

apur.org

248 ms

www.apur.org

416 ms

css_d35cc784c3c19e9db711fd91f1312b41.css

166 ms

js_82acae186624a3c11d14fbe3e228d5bf.js

276 ms

js_415d35718d21324bb1fb7a8bdcb1a50c.js

182 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 93% of them (26 requests) were addressed to the original Apur.org, 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (548 ms) belongs to the original domain Apur.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 184.1 kB (62%)

Content Size

295.2 kB

After Optimization

111.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Apur.org main page is 295.2 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. 20% of websites need less resources to load. CSS take 107.3 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 36.8 kB

  • Original 46.4 kB
  • After minification 42.3 kB
  • After compression 9.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. 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 36.8 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 1.4 kB

  • Original 39.9 kB
  • After minification 38.5 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. Apur images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 58.2 kB

  • Original 101.7 kB
  • After minification 84.6 kB
  • After compression 43.5 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 58.2 kB or 57% of the original size.

CSS Optimization

-82%

Potential reduce by 87.7 kB

  • Original 107.3 kB
  • After minification 104.6 kB
  • After compression 19.6 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. Apur.org needs all CSS files to be minified and compressed as it can save up to 87.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (23%)

Requests Now

26

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

apur.org

apur.org

248 ms

www.apur.org

www.apur.org

416 ms

css_d35cc784c3c19e9db711fd91f1312b41.css

css_d35cc784c3c19e9db711fd91f1312b41.css

166 ms

js_82acae186624a3c11d14fbe3e228d5bf.js

js_82acae186624a3c11d14fbe3e228d5bf.js

276 ms

js_415d35718d21324bb1fb7a8bdcb1a50c.js

js_415d35718d21324bb1fb7a8bdcb1a50c.js

182 ms

L16_760_200.gif

L16_760_200.gif

216 ms

immeubles_acquis_conventionnes_760_200.gif

immeubles_acquis_conventionnes_760_200.gif

280 ms

ACL15E_760_200.gif

ACL15E_760_200.gif

486 ms

Logistique_760_200.gif

Logistique_760_200.gif

481 ms

Crematorium_760_200.gif

Crematorium_760_200.gif

356 ms

visuel_archive_placebo.png

visuel_archive_placebo.png

214 ms

visuel142x114.png

visuel142x114.png

330 ms

ept_metropole_grand_paris_actu.gif

ept_metropole_grand_paris_actu.gif

275 ms

grand_paris_express_lieux_culturels_actu.gif

grand_paris_express_lieux_culturels_actu.gif

452 ms

cooperation_phnom_penh_actu.gif

cooperation_phnom_penh_actu.gif

369 ms

home_bullet.png

home_bullet.png

413 ms

logo.png

logo.png

444 ms

logo-facebook.png

logo-facebook.png

459 ms

logo-twitter.png

logo-twitter.png

494 ms

logo-googleplus.png

logo-googleplus.png

533 ms

logo-linkedin.png

logo-linkedin.png

539 ms

bullet-footer.png

bullet-footer.png

548 ms

ga.js

ga.js

32 ms

boost-gzip-cookie-test.html

boost-gzip-cookie-test.html

468 ms

ajax-loader.gif

ajax-loader.gif

454 ms

bullets.png

bullets.png

457 ms

__utm.gif

__utm.gif

91 ms

css_f8c3e92da0277ee505969992d2c4fdd8.css

css_f8c3e92da0277ee505969992d2c4fdd8.css

85 ms

Accessibility Review

apur.org accessibility score

62

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

Form elements do not have associated labels

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

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 IDs are not unique

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

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>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

apur.org best practices score

75

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

Page has valid source maps

SEO Factors

apur.org SEO score

98

Search Engine Optimization Advices

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

    FR

  • Language Claimed

    FR

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Apur.org can be misinterpreted by Google and other search engines. Our service has detected that French is used on the page, and it matches the claimed language. Our system also found out that Apur.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

apur.org

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