Tools & Wizards About Us
simply-mary.be screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

simply-mary.be

épilation près de Liège ? l'institut de beauté Simply Mary vous accueille

Page Load Speed

5.1 sec in total

First Response

926 ms

Resources Loaded

4 sec

Page Rendered

175 ms

simply-mary.be screenshot

About Website

Click here to check amazing Simply Mary content. Otherwise, check out these important facts you probably never knew about simply-mary.be

Mary Criminisi esthéticienne

Visit simply-mary.be

Key Findings

We analyzed Simply-mary.be page load time and found that the first response time was 926 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

simply-mary.be performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value10.3 s

8/100

10%

TBT (Total Blocking Time)

Value310 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value12.7 s

14/100

10%

Network Requests Diagram

www.simply-mary.be

926 ms

style.css

123 ms

css

25 ms

css

37 ms

css

45 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 84% of them (38 requests) were addressed to the original Simply-mary.be, 7% (3 requests) were made to Fonts.googleapis.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (926 ms) belongs to the original domain Simply-mary.be.

Page Optimization Overview & Recommendations

Page size can be reduced by 320.7 kB (49%)

Content Size

650.4 kB

After Optimization

329.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Simply-mary.be main page is 650.4 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. 35% of websites need less resources to load. Javascripts take 361.5 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 15.7 kB

  • Original 20.6 kB
  • After minification 19.1 kB
  • After compression 4.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 15.7 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 5.1 kB

  • Original 192.3 kB
  • After minification 187.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. Simply Mary images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 237.7 kB

  • Original 361.5 kB
  • After minification 347.5 kB
  • After compression 123.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 237.7 kB or 66% of the original size.

CSS Optimization

-82%

Potential reduce by 62.2 kB

  • Original 75.9 kB
  • After minification 59.6 kB
  • After compression 13.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. Simply-mary.be needs all CSS files to be minified and compressed as it can save up to 62.2 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (73%)

Requests Now

44

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.simply-mary.be

www.simply-mary.be

926 ms

style.css

style.css

123 ms

css

css

25 ms

css

css

37 ms

css

css

45 ms

shortcodes.css

shortcodes.css

287 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

180 ms

page_templates.css

page_templates.css

186 ms

jquery.js

jquery.js

367 ms

et_shortcodes_frontend.js

et_shortcodes_frontend.js

294 ms

plugin.css

plugin.css

219 ms

datatables.css

datatables.css

273 ms

jsapi

jsapi

17 ms

mappress_lib.min.js

mappress_lib.min.js

458 ms

mappress.min.js

mappress.min.js

347 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

436 ms

superfish.js

superfish.js

397 ms

custom.js

custom.js

399 ms

jquery.datatables.min.js

jquery.datatables.min.js

533 ms

jquery.easing-1.3.pack.js

jquery.easing-1.3.pack.js

467 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

490 ms

et-ptemplates-frontend.js

et-ptemplates-frontend.js

530 ms

footer-bg.png

footer-bg.png

162 ms

right-shadow.png

right-shadow.png

169 ms

left-shadow.png

left-shadow.png

177 ms

logo-large-XL1.png

logo-large-XL1.png

220 ms

ajax-loader.gif

ajax-loader.gif

264 ms

simply-mary-criminisi.jpg

simply-mary-criminisi.jpg

353 ms

active-bottom-shadow.png

active-bottom-shadow.png

264 ms

Tarifs-%C3%A9pilation-Soins-du-corps.jpg

Tarifs-%C3%A9pilation-Soins-du-corps.jpg

343 ms

simply-mary-jojoba.jpg

simply-mary-jojoba.jpg

446 ms

simply-mary-acces.jpg

simply-mary-acces.jpg

444 ms

mappress.css

mappress.css

278 ms

js

js

24 ms

down-arrow.png

down-arrow.png

101 ms

footer-top-bg.png

footer-top-bg.png

101 ms

footer-widgets-bg.png

footer-widgets-bg.png

96 ms

ga.js

ga.js

26 ms

__utm.gif

__utm.gif

67 ms

featured-title-bg.png

featured-title-bg.png

104 ms

description-bg.png

description-bg.png

276 ms

active-left-shadow.png

active-left-shadow.png

96 ms

active-right-shadow.png

active-right-shadow.png

102 ms

featured_active_link.png

featured_active_link.png

185 ms

next-slide-overlay.png

next-slide-overlay.png

102 ms

Accessibility Review

simply-mary.be accessibility score

100

Accessibility Issues

Best Practices

simply-mary.be best practices score

67

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

simply-mary.be SEO score

71

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

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 Simply-mary.be 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 Simply-mary.be 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

simply-mary.be

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