Tools & Wizards About Us
1lettre1sourire.org screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

1lettre1sourire.org

1 letter 1 sourire (en) – 1 Lettre 1 Sourire

Page Load Speed

23.8 sec in total

First Response

2.5 sec

Resources Loaded

20.9 sec

Page Rendered

444 ms

1lettre1sourire.org screenshot

About Website

Visit 1lettre1sourire.org now to see the best up-to-date 1 Lettre Sourire content and also check out these interesting facts you probably never knew about 1lettre1sourire.org

Visit 1lettre1sourire.org

Key Findings

We analyzed 1lettre1sourire.org page load time and found that the first response time was 2.5 sec and then it took 21.3 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

1lettre1sourire.org performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.9 s

0/100

10%

LCP (Largest Contentful Paint)

Value18.9 s

0/100

25%

SI (Speed Index)

Value24.7 s

0/100

10%

TBT (Total Blocking Time)

Value4,480 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.221

56/100

15%

TTI (Time to Interactive)

Value22.8 s

1/100

10%

Network Requests Diagram

2527 ms

dashicons.min.css

1031 ms

chatbox.css

1359 ms

wpedon.css

941 ms

block-editor.min.css

939 ms

Our browser made a total of 128 requests to load all elements on the main page. We found that 80% of them (103 requests) were addressed to the original 1lettre1sourire.org, 9% (12 requests) were made to Unpkg.com and 7% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (6.1 sec) belongs to the original domain 1lettre1sourire.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 963.0 kB (40%)

Content Size

2.4 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 1lettre1sourire.org main page is 2.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 746.5 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 546.4 kB

  • Original 677.6 kB
  • After minification 672.4 kB
  • After compression 131.2 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 546.4 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 38.1 kB

  • Original 746.5 kB
  • After minification 708.4 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. 1 Lettre Sourire images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 94.9 kB

  • Original 473.9 kB
  • After minification 472.7 kB
  • After compression 379.0 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 94.9 kB or 20% of the original size.

CSS Optimization

-57%

Potential reduce by 283.6 kB

  • Original 498.9 kB
  • After minification 496.3 kB
  • After compression 215.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. 1lettre1sourire.org needs all CSS files to be minified and compressed as it can save up to 283.6 kB or 57% of the original size.

Requests Breakdown

Number of requests can be reduced by 101 (94%)

Requests Now

108

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

2527 ms

dashicons.min.css

dashicons.min.css

1031 ms

chatbox.css

chatbox.css

1359 ms

wpedon.css

wpedon.css

941 ms

block-editor.min.css

block-editor.min.css

939 ms

hello-asso-public.css

hello-asso-public.css

941 ms

leaflet.css

leaflet.css

1805 ms

Control.Geocoder.css

Control.Geocoder.css

45 ms

MarkerCluster.css

MarkerCluster.css

52 ms

MarkerCluster.Default.css

MarkerCluster.Default.css

53 ms

gf_leaflet.css

gf_leaflet.css

1803 ms

htbbootstrap.css

htbbootstrap.css

1813 ms

all.min.css

all.min.css

1808 ms

animation.css

animation.css

1805 ms

htmega-keyframes.css

htmega-keyframes.css

2276 ms

htmega-global-style.css

htmega-global-style.css

2930 ms

style.min.css

style.min.css

2840 ms

style.css

style.css

2750 ms

simple-line-icons.min.css

simple-line-icons.min.css

2752 ms

menu.css

menu.css

2750 ms

popup.css

popup.css

3222 ms

pum-site-styles.css

pum-site-styles.css

3651 ms

formreset.min.css

formreset.min.css

3650 ms

formsmain.min.css

formsmain.min.css

3654 ms

readyclass.min.css

readyclass.min.css

3648 ms

browsers.min.css

browsers.min.css

4054 ms

gf-preview.css

gf-preview.css

3648 ms

elementor-icons.min.css

elementor-icons.min.css

4524 ms

frontend.min.css

frontend.min.css

4525 ms

swiper.min.css

swiper.min.css

4528 ms

e-swiper.min.css

e-swiper.min.css

4527 ms

post-20.css

post-20.css

4528 ms

popup.min.css

popup.min.css

4948 ms

widget-spacer.min.css

widget-spacer.min.css

5359 ms

widget-image.min.css

widget-image.min.css

5358 ms

widget-heading.min.css

widget-heading.min.css

5361 ms

widget-text-editor.min.css

widget-text-editor.min.css

5360 ms

widget-counter.min.css

widget-counter.min.css

5360 ms

css

css

48 ms

Control.Geocoder.js

Control.Geocoder.js

50 ms

leaflet.markercluster.js

leaflet.markercluster.js

41 ms

Control.Geocoder.css

Control.Geocoder.css

11 ms

leaflet.markercluster.js

leaflet.markercluster.js

23 ms

MarkerCluster.css

MarkerCluster.css

12 ms

MarkerCluster.Default.css

MarkerCluster.Default.css

15 ms

Control.Geocoder.css

Control.Geocoder.css

11 ms

Control.Geocoder.js

Control.Geocoder.js

22 ms

Control.Geocoder.js

Control.Geocoder.js

19 ms

23 ms

widget-divider.min.css

widget-divider.min.css

5501 ms

widget-image-carousel.min.css

widget-image-carousel.min.css

5293 ms

post-2782.css

post-2782.css

5746 ms

general.min.css

general.min.css

5294 ms

widgets.css

widgets.css

5295 ms

style.min.css

style.min.css

5202 ms

jquery.min.js

jquery.min.js

5338 ms

jquery-migrate.min.js

jquery-migrate.min.js

4890 ms

hello-asso-public.js

hello-asso-public.js

4903 ms

leaflet.js

leaflet.js

4973 ms

menu.js

menu.js

4894 ms

home-page.js

home-page.js

5753 ms

jquery.json.min.js

jquery.json.min.js

5704 ms

gravityforms.min.js

gravityforms.min.js

4915 ms

utils.min.js

utils.min.js

4914 ms

conditional_logic.min.js

conditional_logic.min.js

4913 ms

underscore.min.js

underscore.min.js

5134 ms

backbone.min.js

backbone.min.js

5509 ms

api-request.min.js

api-request.min.js

5234 ms

wp-api.min.js

wp-api.min.js

4808 ms

app.js

app.js

4813 ms

css

css

16 ms

wpedon.js

wpedon.js

5210 ms

letter.js

letter.js

5223 ms

gtm4wp-form-move-tracker.js

gtm4wp-form-move-tracker.js

6083 ms

popper.min.js

popper.min.js

5220 ms

htbbootstrap.js

htbbootstrap.js

5211 ms

waypoints.js

waypoints.js

5209 ms

htmega-widgets-active.js

htmega-widgets-active.js

5217 ms

imagesloaded.min.js

imagesloaded.min.js

5208 ms

theme.min.js

theme.min.js

5216 ms

drop-down-mobile-menu.min.js

drop-down-mobile-menu.min.js

5196 ms

drop-down-search.min.js

drop-down-search.min.js

4787 ms

magnific-popup.min.js

magnific-popup.min.js

4788 ms

ow-lightbox.min.js

ow-lightbox.min.js

4785 ms

flickity.pkgd.min.js

flickity.pkgd.min.js

4788 ms

ow-slider.min.js

ow-slider.min.js

4792 ms

scroll-effect.min.js

scroll-effect.min.js

4783 ms

scroll-top.min.js

scroll-top.min.js

4328 ms

select.min.js

select.min.js

4327 ms

flickr.min.js

flickr.min.js

4325 ms

core.min.js

core.min.js

4323 ms

pum-site-scripts.js

pum-site-scripts.js

3869 ms

dom-ready.min.js

dom-ready.min.js

4271 ms

hooks.min.js

hooks.min.js

4259 ms

i18n.min.js

i18n.min.js

4260 ms

a11y.min.js

a11y.min.js

4260 ms

vendor-theme.min.js

vendor-theme.min.js

4172 ms

gtm.js

gtm.js

167 ms

scripts-theme.min.js

scripts-theme.min.js

3301 ms

akismet-frontend.js

akismet-frontend.js

4171 ms

jquery-numerator.min.js

jquery-numerator.min.js

4169 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

4171 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX9-p7K4GLs.ttf

30 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX9-p7K4GLs.ttf

56 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX9-p7K4GLs.ttf

150 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX9-p7K4GLs.ttf

69 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX9-p7K4GLs.ttf

68 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX9-p7K4GLs.ttf

69 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX9-p7K4GLs.ttf

69 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX9-p7K4GLs.ttf

123 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX9-p7K4GLs.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX9-p7K4GLs.ttf

105 ms

general.min.js

general.min.js

3864 ms

social.js

social.js

3857 ms

mailchimp.min.js

mailchimp.min.js

3388 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

4267 ms

webpack.runtime.min.js

webpack.runtime.min.js

4270 ms

frontend-modules.min.js

frontend-modules.min.js

4213 ms

frontend.min.js

frontend.min.js

4309 ms

frontend.min.js

frontend.min.js

3857 ms

elements-handlers.min.js

elements-handlers.min.js

3459 ms

Simple-Line-Icons.ttf

Simple-Line-Icons.ttf

3853 ms

eicons.woff

eicons.woff

4030 ms

fa-brands-400.ttf

fa-brands-400.ttf

4044 ms

4465 ms

PEP24-1300-X-644.jpg

PEP24-1300-X-644.jpg

4034 ms

cropped-logo-sans-fond_result.webp

cropped-logo-sans-fond_result.webp

2212 ms

Copie-de-Copie-de-Copie-de-Copie-de-1-pzeu2s6vk65uoqm8clnf3cey5b318wpt6bn1s5qgqs.png

Copie-de-Copie-de-Copie-de-Copie-de-1-pzeu2s6vk65uoqm8clnf3cey5b318wpt6bn1s5qgqs.png

2681 ms

facteur-1-lettre-1-sourire.gif

facteur-1-lettre-1-sourire.gif

2770 ms

Accessibility Review

1lettre1sourire.org accessibility score

88

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

[aria-*] attributes do not match their roles

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

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

Links do not have a discernible name

Best Practices

1lettre1sourire.org 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

1lettre1sourire.org SEO score

86

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 1lettre1sourire.org 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 1lettre1sourire.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

1lettre1sourire.org

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