Tools & Wizards About Us
signegeneve.ch screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

signegeneve.ch

Signé Genève: Le site communautaire pour publier vos actualités

Page Load Speed

3.6 sec in total

First Response

398 ms

Resources Loaded

1.9 sec

Page Rendered

1.3 sec

signegeneve.ch screenshot

About Website

Welcome to signegeneve.ch homepage info - get ready to check Signegeneve best content for Switzerland right away, or after learning these important things about signegeneve.ch

Retrouvez, partagez et commentez les histoires qui illustrent votre quotidien. Vous êtes curieux, amoureux de votre coin de vie? Dites-le sur Signé Genève!

Visit signegeneve.ch

Key Findings

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

Performance Metrics

signegeneve.ch performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value5,640 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.619

10/100

15%

TTI (Time to Interactive)

Value23.9 s

1/100

10%

Network Requests Diagram

signegeneve.ch

398 ms

signe-geneve

310 ms

tcf.stub.js

151 ms

tinypass.min.js

178 ms

ari-ci.js

176 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Signegeneve.ch, 38% (23 requests) were made to Cdn.unitycms.io and 37% (22 requests) were made to Tdg.ch. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Cdn.unitycms.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 332.2 kB (8%)

Content Size

4.3 MB

After Optimization

4.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Signegeneve.ch main page is 4.3 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. Only a small number of websites need less resources to load. Images take 3.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 286.2 kB

  • Original 345.2 kB
  • After minification 345.1 kB
  • After compression 59.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. 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 286.2 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 44.7 kB

  • Original 3.1 MB
  • After minification 3.1 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. Signegeneve images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 896 B

  • Original 848.2 kB
  • After minification 848.2 kB
  • After compression 847.3 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

-1%

Potential reduce by 455 B

  • Original 41.8 kB
  • After minification 41.8 kB
  • After compression 41.3 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. Signegeneve.ch has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 29 (51%)

Requests Now

57

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

signegeneve.ch

signegeneve.ch

398 ms

signe-geneve

signe-geneve

310 ms

tcf.stub.js

tcf.stub.js

151 ms

tinypass.min.js

tinypass.min.js

178 ms

ari-ci.js

ari-ci.js

176 ms

bdd8baecc000dc0b.css

bdd8baecc000dc0b.css

26 ms

17156820599aad70.css

17156820599aad70.css

39 ms

a66746cb07f4c71b.css

a66746cb07f4c71b.css

53 ms

3e3a0fef2a96842c.css

3e3a0fef2a96842c.css

57 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

52 ms

otSDKStub.js

otSDKStub.js

203 ms

webpack-edf29c3a481a05ea.js

webpack-edf29c3a481a05ea.js

52 ms

framework-0239d17237135aae.js

framework-0239d17237135aae.js

130 ms

main-63ba5981246a5b48.js

main-63ba5981246a5b48.js

135 ms

_app-ea9f2ff5831f31a9.js

_app-ea9f2ff5831f31a9.js

147 ms

63-110d2db3f111f6f2.js

63-110d2db3f111f6f2.js

130 ms

565-99e234a5bbf9d090.js

565-99e234a5bbf9d090.js

130 ms

416-6b780241b86b2ae4.js

416-6b780241b86b2ae4.js

138 ms

96-3ccaa6d568c2a3ee.js

96-3ccaa6d568c2a3ee.js

132 ms

876-f7658f204434cc98.js

876-f7658f204434cc98.js

129 ms

462-850d227e876fe261.js

462-850d227e876fe261.js

131 ms

76-935fca2db14e05ee.js

76-935fca2db14e05ee.js

137 ms

405-f982baabd921a507.js

405-f982baabd921a507.js

135 ms

list-5886f2f577c01beb.js

list-5886f2f577c01beb.js

140 ms

_buildManifest.js

_buildManifest.js

136 ms

_ssgManifest.js

_ssgManifest.js

139 ms

1P8eB_N6qXF8aP3vA0nHYb.png

1P8eB_N6qXF8aP3vA0nHYb.png

149 ms

AtiNEQ4PKXZAkMxIr9X5mk.jpg

AtiNEQ4PKXZAkMxIr9X5mk.jpg

1068 ms

8Jx4hS3t4kRAmNnIiX4aWn.png

8Jx4hS3t4kRAmNnIiX4aWn.png

174 ms

9-P6PFxRaOEB7kID8IW4Aw.jpg

9-P6PFxRaOEB7kID8IW4Aw.jpg

169 ms

3-AZQdJmanY8Tl9rIgdFxL.jpg

3-AZQdJmanY8Tl9rIgdFxL.jpg

171 ms

9OhiPnwOqxdBUl1luGD59Y.png

9OhiPnwOqxdBUl1luGD59Y.png

167 ms

8aqX2nazq5f9eG5s8gWsKF.jpg

8aqX2nazq5f9eG5s8gWsKF.jpg

169 ms

D0kfmbL24lXAGmjyt3gvLA.jpg

D0kfmbL24lXAGmjyt3gvLA.jpg

172 ms

F4m1j9fr4Cw8IRxDDjErUp.jpg

F4m1j9fr4Cw8IRxDDjErUp.jpg

171 ms

AIHx9Atrqq69R4TNHHewgQ.jpg

AIHx9Atrqq69R4TNHHewgQ.jpg

171 ms

4_AKCmrBK8f8yShoKuTntQ.jpg

4_AKCmrBK8f8yShoKuTntQ.jpg

171 ms

02FHZhwwK1g8YfqJix4d9X.jpg

02FHZhwwK1g8YfqJix4d9X.jpg

175 ms

05xiAcMAKshBBD37nfZBqO.jpg

05xiAcMAKshBBD37nfZBqO.jpg

177 ms

9f5Zji_0KKO99gomh3R9Rz.jpg

9f5Zji_0KKO99gomh3R9Rz.jpg

175 ms

3vhC2DSJaFoATZnN0Nayu-.jpg

3vhC2DSJaFoATZnN0Nayu-.jpg

178 ms

ErNuBmESKbE9f1PnfW69c3.jpg

ErNuBmESKbE9f1PnfW69c3.jpg

177 ms

FzgTc14YqNV8zvfIXNQjpu.jpg

FzgTc14YqNV8zvfIXNQjpu.jpg

179 ms

8YOHavSWaUVAx_KtBk56Tn.jpg

8YOHavSWaUVAx_KtBk56Tn.jpg

178 ms

1UcVjeb3qrP82PW1gaaYXH.jpg

1UcVjeb3qrP82PW1gaaYXH.jpg

179 ms

3UEMK7pqauAAEcqCqD7hwe.jpg

3UEMK7pqauAAEcqCqD7hwe.jpg

182 ms

7JgG1ngLa708qMTI2cutKh.jpg

7JgG1ngLa708qMTI2cutKh.jpg

180 ms

4VZW2G1mq7xB7l_ifB_2em.jpg

4VZW2G1mq7xB7l_ifB_2em.jpg

181 ms

FVdSfU23KOGAM_vMDJmrAB.jpg

FVdSfU23KOGAM_vMDJmrAB.jpg

182 ms

logo_tdg_short.adbd8445.svg

logo_tdg_short.adbd8445.svg

24 ms

piano.es5.js

piano.es5.js

108 ms

3828236b-ab35-4cfa-bf6e-4275e65cb818.json

3828236b-ab35-4cfa-bf6e-4275e65cb818.json

85 ms

location

location

128 ms

otBannerSdk.js

otBannerSdk.js

20 ms

fr.json

fr.json

51 ms

iab2V2Data.json

iab2V2Data.json

47 ms

otTCF.js

otTCF.js

30 ms

purposes-fr.json

purposes-fr.json

19 ms

otFlat.json

otFlat.json

24 ms

otCommonStyles.css

otCommonStyles.css

19 ms

Accessibility Review

signegeneve.ch accessibility score

89

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

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

Heading elements are not in a sequentially-descending order

Best Practices

signegeneve.ch 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

signegeneve.ch SEO score

100

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

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 Signegeneve.ch 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 Signegeneve.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

signegeneve.ch

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