Tools & Wizards About Us
plan.epfl.ch screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

plan.epfl.ch

EPFL - PLAN

Page Load Speed

6.3 sec in total

First Response

587 ms

Resources Loaded

5.2 sec

Page Rendered

525 ms

plan.epfl.ch screenshot

About Website

Visit plan.epfl.ch now to see the best up-to-date PLAN EPFL content for Switzerland and also check out these interesting facts you probably never knew about plan.epfl.ch

Visit plan.epfl.ch

Key Findings

We analyzed Plan.epfl.ch page load time and found that the first response time was 587 ms and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

plan.epfl.ch performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value10.9 s

6/100

10%

TBT (Total Blocking Time)

Value7,910 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

plan.epfl.ch

587 ms

ext-all.css

107 ms

xtheme-gray.css

189 ms

epfl.css

195 ms

api.css

192 ms

Our browser made a total of 139 requests to load all elements on the main page. We found that 29% of them (40 requests) were addressed to the original Plan.epfl.ch, 17% (24 requests) were made to Plan-epfl-wmts0.epfl.ch and 14% (20 requests) were made to Plan-osm-tile0.epfl.ch. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Plan-osm-tile0.epfl.ch.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (47%)

Content Size

3.0 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Plan.epfl.ch main page is 3.0 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. 60% of websites need less resources to load. Javascripts take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 75.1 kB

  • Original 85.0 kB
  • After minification 79.6 kB
  • After compression 9.9 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 75.1 kB or 88% of the original size.

Image Optimization

-5%

Potential reduce by 66.2 kB

  • Original 1.2 MB
  • After minification 1.2 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. PLAN EPFL images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 1.1 MB

  • Original 1.6 MB
  • After minification 1.5 MB
  • After compression 412.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 1.1 MB or 73% of the original size.

CSS Optimization

-84%

Potential reduce by 140.4 kB

  • Original 167.1 kB
  • After minification 149.3 kB
  • After compression 26.7 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. Plan.epfl.ch needs all CSS files to be minified and compressed as it can save up to 140.4 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (33%)

Requests Now

137

After Optimization

92

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

plan.epfl.ch

plan.epfl.ch

587 ms

ext-all.css

ext-all.css

107 ms

xtheme-gray.css

xtheme-gray.css

189 ms

epfl.css

epfl.css

195 ms

api.css

api.css

192 ms

epflheader.css

epflheader.css

191 ms

epfl_small.png

epfl_small.png

567 ms

ext-base.js

ext-base.js

213 ms

ext-all.js

ext-all.js

496 ms

jquery-epfl.min.js

jquery-epfl.min.js

473 ms

epfl.js

epfl.js

669 ms

app.js

app.js

387 ms

loading_white_bg.gif

loading_white_bg.gif

96 ms

underline.gif

underline.gif

97 ms

sprites-arrow.png

sprites-arrow.png

190 ms

sprites.png

sprites.png

191 ms

magnifier.png

magnifier.png

272 ms

slash.png

slash.png

284 ms

separator.png

separator.png

346 ms

main-navigation.png

main-navigation.png

357 ms

ga.js

ga.js

28 ms

__utm.gif

__utm.gif

419 ms

__utm.gif

__utm.gif

519 ms

tip-sprite.gif

tip-sprite.gif

481 ms

Aerial

Aerial

471 ms

style.css

style.css

460 ms

0.png

0.png

475 ms

0.png

0.png

468 ms

23177.png

23177.png

558 ms

23178.png

23178.png

481 ms

33965.png

33965.png

188 ms

33962.png

33962.png

284 ms

23177.png

23177.png

378 ms

23178.png

23178.png

462 ms

23179.png

23179.png

470 ms

23178.png

23178.png

539 ms

23178.png

23178.png

644 ms

23180.png

23180.png

566 ms

23178.png

23178.png

585 ms

23177.png

23177.png

566 ms

layer-switcher-maximize.png

layer-switcher-maximize.png

129 ms

layer-switcher-minimize.png

layer-switcher-minimize.png

129 ms

wms_themes

wms_themes

127 ms

btn-sprite.gif

btn-sprite.gif

129 ms

icons_map.png

icons_map.png

279 ms

underline.gif

underline.gif

130 ms

tb-btn-sprite.gif

tb-btn-sprite.gif

193 ms

tab-button-bg.png

tab-button-bg.png

188 ms

wms_themes

wms_themes

187 ms

s.gif

s.gif

188 ms

treeplus.png

treeplus.png

179 ms

folder.gif

folder.gif

268 ms

treeminus.png

treeminus.png

269 ms

folder-open.gif

folder-open.gif

269 ms

mini-left.gif

mini-left.gif

277 ms

wms_themes

wms_themes

542 ms

wms_themes

wms_themes

624 ms

23177.png

23177.png

431 ms

23178.png

23178.png

431 ms

23179.png

23179.png

334 ms

23180.png

23180.png

337 ms

23179.png

23179.png

431 ms

23180.png

23180.png

434 ms

23177.png

23177.png

530 ms

23179.png

23179.png

516 ms

23179.png

23179.png

515 ms

23176.png

23176.png

530 ms

1448.png

1448.png

513 ms

1449.png

1449.png

533 ms

33964.png

33964.png

187 ms

33965.png

33965.png

187 ms

33963.png

33963.png

321 ms

33963.png

33963.png

367 ms

33962.png

33962.png

375 ms

33962.png

33962.png

415 ms

33962.png

33962.png

465 ms

23178.png

23178.png

643 ms

23177.png

23177.png

556 ms

23179.png

23179.png

650 ms

23177.png

23177.png

724 ms

23179.png

23179.png

633 ms

23176.png

23176.png

639 ms

23176.png

23176.png

762 ms

23176.png

23176.png

725 ms

23180.png

23180.png

726 ms

23177.png

23177.png

731 ms

23176.png

23176.png

733 ms

23176.png

23176.png

815 ms

23180.png

23180.png

817 ms

23176.png

23176.png

824 ms

23180.png

23180.png

822 ms

23180.png

23180.png

828 ms

2123.png

2123.png

854 ms

-1.png

-1.png

3302 ms

23178.png

23178.png

280 ms

23177.png

23177.png

280 ms

23179.png

23179.png

280 ms

23177.png

23177.png

284 ms

23179.png

23179.png

194 ms

23176.png

23176.png

299 ms

23176.png

23176.png

369 ms

23176.png

23176.png

371 ms

23180.png

23180.png

372 ms

23177.png

23177.png

370 ms

23176.png

23176.png

392 ms

23176.png

23176.png

460 ms

23180.png

23180.png

468 ms

23176.png

23176.png

471 ms

23180.png

23180.png

470 ms

23180.png

23180.png

471 ms

1448.png

1448.png

641 ms

1449.png

1449.png

557 ms

23178.png

23178.png

474 ms

23179.png

23179.png

394 ms

23178.png

23178.png

473 ms

23178.png

23178.png

468 ms

23180.png

23180.png

389 ms

23178.png

23178.png

474 ms

23177.png

23177.png

558 ms

33964.png

33964.png

176 ms

33963.png

33963.png

185 ms

33966.png

33966.png

181 ms

33965.png

33965.png

185 ms

33966.png

33966.png

189 ms

33963.png

33963.png

190 ms

23178.png

23178.png

545 ms

23177.png

23177.png

551 ms

23178.png

23178.png

556 ms

23179.png

23179.png

481 ms

23180.png

23180.png

484 ms

23179.png

23179.png

650 ms

23180.png

23180.png

558 ms

23177.png

23177.png

720 ms

23179.png

23179.png

621 ms

23179.png

23179.png

627 ms

23176.png

23176.png

628 ms

2122.png

2122.png

633 ms

blank.gif

blank.gif

261 ms

info.json

info.json

319 ms

Accessibility Review

plan.epfl.ch accessibility score

58

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 do not have all required [aria-*] attributes

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

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

plan.epfl.ch best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

plan.epfl.ch SEO score

77

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

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 Plan.epfl.ch 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 Plan.epfl.ch 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

plan.epfl.ch

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