Tools & Wizards About Us
a-way-to-go.com screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 64

    SEO

    Google-friendlier than
    24% of websites

a-way-to-go.com

WAY TO GO

Page Load Speed

565 ms in total

First Response

60 ms

Resources Loaded

422 ms

Page Rendered

83 ms

a-way-to-go.com screenshot

About Website

Visit a-way-to-go.com now to see the best up-to-date A WAY To GO content for Brazil and also check out these interesting facts you probably never knew about a-way-to-go.com

New web project by the creators of BLA BLA and Just a Reflektor. A walk in the woods by Vincent Morisset, Philippe Lambert, Édouard Lanctôt-Benoit & Caroline Robert (AATOAA). Produced by the NFB and F...

Visit a-way-to-go.com

Key Findings

We analyzed A-way-to-go.com page load time and found that the first response time was 60 ms and then it took 505 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

a-way-to-go.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value2.0 s

99/100

10%

TBT (Total Blocking Time)

Value530 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value7.7 s

45/100

10%

Network Requests Diagram

a-way-to-go.com

60 ms

fonts.css

60 ms

jquery.onf-nfb.min.css

58 ms

main.min.css

57 ms

textes.js

62 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original A-way-to-go.com, 45% (15 requests) were made to Media1.jusqu-ici.com and 21% (7 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (328 ms) relates to the external source Static.francetv.fr.

Page Optimization Overview & Recommendations

Page size can be reduced by 19.7 kB (5%)

Content Size

392.8 kB

After Optimization

373.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of A-way-to-go.com main page is 392.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. 30% of websites need less resources to load. Javascripts take 316.6 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 15.6 kB

  • Original 21.6 kB
  • After minification 18.1 kB
  • After compression 6.0 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 3.5 kB, which is 16% 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 15.6 kB or 72% of the original size.

Image Optimization

-6%

Potential reduce by 3.0 kB

  • Original 47.3 kB
  • After minification 44.2 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. A WAY To GO images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 903 B

  • Original 316.6 kB
  • After minification 316.3 kB
  • After compression 315.7 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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 167 B

  • Original 7.3 kB
  • After minification 7.3 kB
  • After compression 7.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. A-way-to-go.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 13 (42%)

Requests Now

31

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

a-way-to-go.com

a-way-to-go.com

60 ms

fonts.css

fonts.css

60 ms

jquery.onf-nfb.min.css

jquery.onf-nfb.min.css

58 ms

main.min.css

main.min.css

57 ms

textes.js

textes.js

62 ms

config.js

config.js

25 ms

jquery.min.js

jquery.min.js

49 ms

jquery.onf-nfb.min.js

jquery.onf-nfb.min.js

43 ms

site.min.js

site.min.js

76 ms

main.min.js

main.min.js

38 ms

audience-min.js

audience-min.js

328 ms

bt_fermer_b.png

bt_fermer_b.png

41 ms

ic_pause.png

ic_pause.png

59 ms

bt_partager.png

bt_partager.png

59 ms

pays.php

pays.php

52 ms

analytics.js

analytics.js

57 ms

logos_debut_en.jpg

logos_debut_en.jpg

41 ms

titre_en.png

titre_en.png

39 ms

controls_debut_g_en.png

controls_debut_g_en.png

171 ms

controls_debut_d_en.png

controls_debut_d_en.png

152 ms

controls_fin_en.png

controls_fin_en.png

153 ms

collect

collect

42 ms

collect

collect

51 ms

collect

collect

15 ms

texture_splash.gif

texture_splash.gif

15 ms

logo_sundance.png

logo_sundance.png

15 ms

logo_fwa_people_en.png

logo_fwa_people_en.png

11 ms

logo_webby_vr.png

logo_webby_vr.png

10 ms

js

js

63 ms

collect

collect

4 ms

collect

collect

7 ms

collect

collect

6 ms

audience-min.js

audience-min.js

28 ms

Accessibility Review

a-way-to-go.com accessibility score

100

Accessibility Issues

Best Practices

a-way-to-go.com 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

a-way-to-go.com SEO score

64

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

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 A-way-to-go.com 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 A-way-to-go.com 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

a-way-to-go.com

Open Graph data is detected on the main page of A WAY To GO. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: