Tools & Wizards About Us
weddingwonderlandcakes.com screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

weddingwonderlandcakes.com

Home - Temmtations by Wedding Wonderland in St. Louis, Missouri

Page Load Speed

3.6 sec in total

First Response

313 ms

Resources Loaded

3.2 sec

Page Rendered

71 ms

weddingwonderlandcakes.com screenshot

About Website

Visit weddingwonderlandcakes.com now to see the best up-to-date Wedding Wonderland Cakes content for United States and also check out these interesting facts you probably never knew about weddingwonderlandcakes.com

Wedding Cakes, Specialty Cakes for all occasions

Visit weddingwonderlandcakes.com

Key Findings

We analyzed Weddingwonderlandcakes.com page load time and found that the first response time was 313 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 60% of websites can load faster.

Performance Metrics

weddingwonderlandcakes.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value17.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.0 s

0/100

25%

SI (Speed Index)

Value23.9 s

0/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.036

100/100

15%

TTI (Time to Interactive)

Value30.7 s

0/100

10%

Network Requests Diagram

weddingwonderlandcakes.com

313 ms

style.min.css

232 ms

styles.css

176 ms

rs6.css

291 ms

style.css

176 ms

Our browser made a total of 101 requests to load all elements on the main page. We found that 88% of them (89 requests) were addressed to the original Weddingwonderlandcakes.com, 10% (10 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (749 ms) belongs to the original domain Weddingwonderlandcakes.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.7 MB (64%)

Content Size

4.2 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weddingwonderlandcakes.com main page is 4.2 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. 70% of websites need less resources to load. Javascripts take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 56.9 kB

  • Original 72.1 kB
  • After minification 69.5 kB
  • After compression 15.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 56.9 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 140 B

  • Original 781.7 kB
  • After minification 781.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. Wedding Wonderland Cakes images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 1.2 MB

  • Original 1.7 MB
  • After minification 1.7 MB
  • After compression 506.2 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 1.2 MB or 70% of the original size.

CSS Optimization

-88%

Potential reduce by 1.4 MB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 187.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. Weddingwonderlandcakes.com needs all CSS files to be minified and compressed as it can save up to 1.4 MB or 88% of the original size.

Requests Breakdown

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

Requests Now

89

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weddingwonderlandcakes.com

weddingwonderlandcakes.com

313 ms

style.min.css

style.min.css

232 ms

styles.css

styles.css

176 ms

rs6.css

rs6.css

291 ms

style.css

style.css

176 ms

modules.min.css

modules.min.css

523 ms

dripicons.css

dripicons.css

180 ms

style.min.css

style.min.css

293 ms

fontawesome-all.min.css

fontawesome-all.min.css

294 ms

ionicons.min.css

ionicons.min.css

298 ms

style.css

style.css

296 ms

style.css

style.css

352 ms

simple-line-icons.css

simple-line-icons.css

353 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

354 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

354 ms

woocommerce.min.css

woocommerce.min.css

415 ms

woocommerce-responsive.min.css

woocommerce-responsive.min.css

412 ms

style_dynamic.css

style_dynamic.css

412 ms

modules-responsive.min.css

modules-responsive.min.css

418 ms

style_dynamic_responsive.css

style_dynamic_responsive.css

413 ms

css

css

27 ms

core-dashboard.min.css

core-dashboard.min.css

472 ms

js_composer.min.css

js_composer.min.css

703 ms

jquery.min.js

jquery.min.js

475 ms

jquery-migrate.min.js

jquery-migrate.min.js

476 ms

itro-scripts.js

itro-scripts.js

474 ms

rbtools.min.js

rbtools.min.js

645 ms

rs6.min.js

rs6.min.js

749 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

538 ms

add-to-cart.min.js

add-to-cart.min.js

538 ms

js.cookie.min.js

js.cookie.min.js

581 ms

woocommerce.min.js

woocommerce.min.js

597 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

598 ms

select2.full.min.js

select2.full.min.js

641 ms

css

css

16 ms

wc-blocks.css

wc-blocks.css

607 ms

react.min.js

react.min.js

607 ms

react-jsx-runtime.min.js

react-jsx-runtime.min.js

697 ms

autop.min.js

autop.min.js

697 ms

blob.min.js

blob.min.js

606 ms

block-serialization-default-parser.min.js

block-serialization-default-parser.min.js

605 ms

hooks.min.js

hooks.min.js

647 ms

deprecated.min.js

deprecated.min.js

594 ms

dom.min.js

dom.min.js

534 ms

react-dom.min.js

react-dom.min.js

533 ms

escape-html.min.js

escape-html.min.js

531 ms

element.min.js

element.min.js

531 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

544 ms

i18n.min.js

i18n.min.js

489 ms

keycodes.min.js

keycodes.min.js

489 ms

priority-queue.min.js

priority-queue.min.js

488 ms

compose.min.js

compose.min.js

498 ms

private-apis.min.js

private-apis.min.js

437 ms

redux-routine.min.js

redux-routine.min.js

476 ms

data.min.js

data.min.js

480 ms

html-entities.min.js

html-entities.min.js

473 ms

dom-ready.min.js

dom-ready.min.js

474 ms

a11y.min.js

a11y.min.js

429 ms

rich-text.min.js

rich-text.min.js

438 ms

shortcode.min.js

shortcode.min.js

474 ms

blocks.min.js

blocks.min.js

483 ms

index.js

index.js

417 ms

index.js

index.js

415 ms

index.js

index.js

425 ms

sourcebuster.min.js

sourcebuster.min.js

388 ms

order-attribution.min.js

order-attribution.min.js

409 ms

core.min.js

core.min.js

416 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

374 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

371 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

368 ms

jquery.appear.js

jquery.appear.js

372 ms

modernizr.min.js

modernizr.min.js

319 ms

jquery.hoverIntent.min.js

jquery.hoverIntent.min.js

328 ms

jquery.plugin.js

jquery.plugin.js

301 ms

owl.carousel.min.js

owl.carousel.min.js

302 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

305 ms

fluidvids.min.js

fluidvids.min.js

271 ms

perfect-scrollbar.jquery.min.js

perfect-scrollbar.jquery.min.js

305 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

313 ms

parallax.min.js

parallax.min.js

315 ms

jquery.waitforimages.js

jquery.waitforimages.js

314 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

318 ms

H4c0BXOCl9bbnla_nHIq6oGzilJm9otsA9kQq_da4SWs.woff

H4c0BXOCl9bbnla_nHIq6oGzilJm9otsA9kQq_da4SWs.woff

53 ms

H4c2BXOCl9bbnla_nHIA47NMUjsNbCVrFhFTc71q6w.woff

H4c2BXOCl9bbnla_nHIA47NMUjsNbCVrFhFTc71q6w.woff

94 ms

H4c2BXOCl9bbnla_nHIA47NMUjsNbCVrFk9Tc71q6w.woff

H4c2BXOCl9bbnla_nHIA47NMUjsNbCVrFk9Tc71q6w.woff

115 ms

H4c2BXOCl9bbnla_nHIA47NMUjsNbCVrFs9Uc71q6w.woff

H4c2BXOCl9bbnla_nHIA47NMUjsNbCVrFs9Uc71q6w.woff

102 ms

H4c2BXOCl9bbnla_nHIA47NMUjsNbCVrFvZUc71q6w.woff

H4c2BXOCl9bbnla_nHIA47NMUjsNbCVrFvZUc71q6w.woff

102 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFmQkEk50e4.woff

7Aulp_0qiz-aVz7u3PJLcUMYOFmQkEk50e4.woff

67 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk50e4.woff

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk50e4.woff

71 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFkQl0k50e4.woff

7Aulp_0qiz-aVz7u3PJLcUMYOFkQl0k50e4.woff

82 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k50e4.woff

7Aulp_0qiz-aVz7u3PJLcUMYOFkpl0k50e4.woff

83 ms

7Aujp_0qiz-afTfcIyoiGtm2P0wG05Fz4eSVxQ.woff

7Aujp_0qiz-afTfcIyoiGtm2P0wG05Fz4eSVxQ.woff

125 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

325 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

349 ms

packery-mode.pkgd.min.js

packery-mode.pkgd.min.js

360 ms

modules.min.js

modules.min.js

362 ms

js_composer_front.min.js

js_composer_front.min.js

361 ms

ionicons.ttf

ionicons.ttf

414 ms

WWlogo_web2022.png

WWlogo_web2022.png

371 ms

Logo-Word-SM1.png

Logo-Word-SM1.png

374 ms

IMG_8411-scaled.jpg

IMG_8411-scaled.jpg

428 ms

Accessibility Review

weddingwonderlandcakes.com accessibility score

80

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

Links do not have a discernible name

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

weddingwonderlandcakes.com best practices score

92

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

SEO Factors

weddingwonderlandcakes.com 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 Weddingwonderlandcakes.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 Weddingwonderlandcakes.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

weddingwonderlandcakes.com

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