Tools & Wizards About Us
godf.org screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    76% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 42

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

godf.org

Grand Orient de France - Liberté - Egalité - Fraternité

Page Load Speed

3.7 sec in total

First Response

376 ms

Resources Loaded

2.9 sec

Page Rendered

391 ms

godf.org screenshot

About Website

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

symfony project

Visit godf.org

Key Findings

We analyzed Godf.org page load time and found that the first response time was 376 ms and then it took 3.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

godf.org performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value5.4 s

20/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.23

54/100

15%

TTI (Time to Interactive)

Value4.1 s

86/100

10%

Network Requests Diagram

godf.org

376 ms

www.godf.org

805 ms

js

28 ms

prototype.js

585 ms

scriptaculous.js

170 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 49% of them (40 requests) were addressed to the original Godf.org, 29% (24 requests) were made to Maps.google.com and 10% (8 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (1000 ms) belongs to the original domain Godf.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 599.4 kB (32%)

Content Size

1.9 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-83%

Potential reduce by 44.1 kB

  • Original 52.9 kB
  • After minification 49.8 kB
  • After compression 8.8 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 44.1 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 32.3 kB

  • Original 1.1 MB
  • After minification 1.0 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. Godf images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 514.4 kB

  • Original 740.4 kB
  • After minification 680.9 kB
  • After compression 225.9 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 514.4 kB or 69% of the original size.

CSS Optimization

-79%

Potential reduce by 8.6 kB

  • Original 10.8 kB
  • After minification 8.7 kB
  • After compression 2.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. Godf.org needs all CSS files to be minified and compressed as it can save up to 8.6 kB or 79% of the original size.

Requests Breakdown

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

Requests Now

74

After Optimization

41

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

godf.org

godf.org

376 ms

www.godf.org

www.godf.org

805 ms

js

js

28 ms

prototype.js

prototype.js

585 ms

scriptaculous.js

scriptaculous.js

170 ms

map.js

map.js

263 ms

main.css

main.css

363 ms

front.css

front.css

182 ms

Fluster2.packed.js

Fluster2.packed.js

86 ms

builder.js

builder.js

85 ms

effects.js

effects.js

169 ms

dragdrop.js

dragdrop.js

346 ms

controls.js

controls.js

367 ms

slider.js

slider.js

184 ms

a7152a8ce1c025e370e710049e73973e.gif

a7152a8ce1c025e370e710049e73973e.gif

373 ms

footer_bg.gif

footer_bg.gif

582 ms

fondmenu.png

fondmenu.png

149 ms

flag_fr.gif

flag_fr.gif

150 ms

flag_en.gif

flag_en.gif

151 ms

flag_es.gif

flag_es.gif

151 ms

fb_logo.png

fb_logo.png

149 ms

twitter_logo.png

twitter_logo.png

177 ms

fd_menu.gif

fd_menu.gif

220 ms

bleu_container.png

bleu_container.png

179 ms

c4327d55070f59e4a288c3d82027aad3.png

c4327d55070f59e4a288c3d82027aad3.png

456 ms

0beecb8279c66de0542c1a35b6c43cef.jpg

0beecb8279c66de0542c1a35b6c43cef.jpg

457 ms

dbe11fa29c5fa694b7882943445f8eb8.gif

dbe11fa29c5fa694b7882943445f8eb8.gif

265 ms

bae2dbd82fd9cae12f3a88b5e79e6aaa.png

bae2dbd82fd9cae12f3a88b5e79e6aaa.png

589 ms

45486a4cbe79473d7da8019c8d018492.png

45486a4cbe79473d7da8019c8d018492.png

385 ms

newsletter.png

newsletter.png

340 ms

indicator.gif

indicator.gif

419 ms

fd_texte.png

fd_texte.png

473 ms

picto_titre.png

picto_titre.png

504 ms

ebc204e32fe8360083c950b3f291ccb0.jpg

ebc204e32fe8360083c950b3f291ccb0.jpg

1000 ms

e35667a2fd162909389eb5d8b83091d3.png

e35667a2fd162909389eb5d8b83091d3.png

554 ms

0292861ccdb28c4676b9749ff2e0e1d0.gif

0292861ccdb28c4676b9749ff2e0e1d0.gif

559 ms

decc82796e9217f6accb7a1edde2c5f2.png

decc82796e9217f6accb7a1edde2c5f2.png

585 ms

e11407bcc9fc15088b5975b78fa1408d.jpg

e11407bcc9fc15088b5975b78fa1408d.jpg

828 ms

picto_tele.gif

picto_tele.gif

646 ms

devenir_fm.jpg

devenir_fm.jpg

660 ms

common.js

common.js

16 ms

util.js

util.js

16 ms

geocoder.js

geocoder.js

16 ms

map.js

map.js

52 ms

overlay.js

overlay.js

48 ms

StaticMapService.GetMapImage

StaticMapService.GetMapImage

208 ms

ga.js

ga.js

41 ms

__utm.gif

__utm.gif

43 ms

onion.js

onion.js

25 ms

openhand_8_8.cur

openhand_8_8.cur

39 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

130 ms

stats.js

stats.js

19 ms

controls.js

controls.js

14 ms

infowindow.js

infowindow.js

14 ms

transparent.png

transparent.png

47 ms

css

css

41 ms

marker.js

marker.js

19 ms

google4.png

google4.png

34 ms

mapcnt6.png

mapcnt6.png

35 ms

tmapctrl.png

tmapctrl.png

40 ms

cb_scout5.png

cb_scout5.png

71 ms

tmapctrl4.png

tmapctrl4.png

41 ms

imgs8.png

imgs8.png

41 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

38 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

39 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

69 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

70 ms

vt

vt

19 ms

vt

vt

24 ms

vt

vt

11 ms

vt

vt

10 ms

vt

vt

11 ms

vt

vt

18 ms

vt

vt

19 ms

vt

vt

11 ms

vt

vt

17 ms

vt

vt

18 ms

vt

vt

19 ms

vt

vt

21 ms

vt

vt

19 ms

a7152a8ce1c025e370e710049e73973e.gif

a7152a8ce1c025e370e710049e73973e.gif

486 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

16 ms

Accessibility Review

godf.org accessibility score

71

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

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

Form elements do not have associated labels

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

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

godf.org best practices score

42

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

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

godf.org SEO score

83

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

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

godf.org

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