Tools & Wizards About Us
sweetsmarie.com screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

sweetsmarie.com

Sweets Marie Homepage- For all your baked good sweet tooth needs in Amsterdam.

Page Load Speed

1 sec in total

First Response

139 ms

Resources Loaded

714 ms

Page Rendered

152 ms

sweetsmarie.com screenshot

About Website

Visit sweetsmarie.com now to see the best up-to-date Sweets Marie content and also check out these interesting facts you probably never knew about sweetsmarie.com

Sweets Marie - For all your cupcakes, cookies, cakes, pies in Amsterdam. For birthdays, weddings and all events.

Visit sweetsmarie.com

Key Findings

We analyzed Sweetsmarie.com page load time and found that the first response time was 139 ms and then it took 866 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

sweetsmarie.com performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

76/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

27/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.179

68/100

15%

TTI (Time to Interactive)

Value6.0 s

65/100

10%

Network Requests Diagram

sweetsmarie.com

139 ms

screen.css

35 ms

prototype.js

100 ms

tabber.js

68 ms

adsbygoogle.js

396 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 46% of them (19 requests) were addressed to the original Sweetsmarie.com, 20% (8 requests) were made to Static.xx.fbcdn.net and 15% (6 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (396 ms) relates to the external source Pagead2.googlesyndication.com.

Page Optimization Overview & Recommendations

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

Content Size

453.2 kB

After Optimization

431.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sweetsmarie.com main page is 453.2 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. 50% of websites need less resources to load. Images take 233.7 kB which makes up the majority of the site volume.

HTML Optimization

-68%

Potential reduce by 11.1 kB

  • Original 16.4 kB
  • After minification 15.8 kB
  • After compression 5.3 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 11.1 kB or 68% of the original size.

Image Optimization

-0%

Potential reduce by 247 B

  • Original 233.7 kB
  • After minification 233.5 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. Sweets Marie images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 10.1 kB

  • Original 201.0 kB
  • After minification 200.6 kB
  • After compression 191.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. This website has mostly compressed JavaScripts.

CSS Optimization

-19%

Potential reduce by 385 B

  • Original 2.1 kB
  • After minification 2.1 kB
  • After compression 1.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. Sweetsmarie.com needs all CSS files to be minified and compressed as it can save up to 385 B or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (41%)

Requests Now

37

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sweetsmarie.com

sweetsmarie.com

139 ms

screen.css

screen.css

35 ms

prototype.js

prototype.js

100 ms

tabber.js

tabber.js

68 ms

adsbygoogle.js

adsbygoogle.js

396 ms

plusone.js

plusone.js

29 ms

ga.js

ga.js

20 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

12 ms

cb=gapi.loaded_1

cb=gapi.loaded_1

62 ms

fastbutton

fastbutton

58 ms

background.png

background.png

89 ms

sweets-marie-logo.png

sweets-marie-logo.png

74 ms

facebook-icon.png

facebook-icon.png

73 ms

twitter.png

twitter.png

90 ms

home.jpg

home.jpg

163 ms

gradient.png

gradient.png

91 ms

gradient.png

gradient.png

94 ms

bars.jpg

bars.jpg

94 ms

breads.jpg

breads.jpg

121 ms

cakes.jpg

cakes.jpg

123 ms

cookies.jpg

cookies.jpg

124 ms

cupcakes.jpg

cupcakes.jpg

127 ms

muffins.jpg

muffins.jpg

126 ms

pies.jpg

pies.jpg

162 ms

whoopie-pies.jpg

whoopie-pies.jpg

163 ms

likebox.php

likebox.php

160 ms

__utm.gif

__utm.gif

40 ms

postmessageRelay

postmessageRelay

72 ms

developers.google.com

developers.google.com

350 ms

3604799710-postmessagerelay.js

3604799710-postmessagerelay.js

15 ms

rpc:shindig_random.js

rpc:shindig_random.js

7 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

9 ms

eOzOzediAge.css

eOzOzediAge.css

23 ms

VWDhCULazb5.js

VWDhCULazb5.js

30 ms

o1ndYS2og_B.js

o1ndYS2og_B.js

25 ms

5xOV5e9oy4e.js

5xOV5e9oy4e.js

29 ms

mP12tTiNgO_.js

mP12tTiNgO_.js

28 ms

owo2sPJxB2z.js

owo2sPJxB2z.js

26 ms

p55HfXW__mM.js

p55HfXW__mM.js

65 ms

291863789_463026445634190_6577397473830680349_n.jpg

291863789_463026445634190_6577397473830680349_n.jpg

78 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

40 ms

Accessibility Review

sweetsmarie.com accessibility score

76

Accessibility Issues

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.

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

<frame> or <iframe> elements do not have a title

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

High

<html> element does not have a valid value for its [lang] attribute.

Best Practices

sweetsmarie.com 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

SEO Factors

sweetsmarie.com SEO score

77

Search Engine Optimization Advices

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 Sweetsmarie.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 Sweetsmarie.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

sweetsmarie.com

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