Tools & Wizards About Us
mapleleaffudge.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

mapleleaffudge.com

Maple Leaf Fudge in Niagara-on-the-Lake - Fresh fudge daily!

Page Load Speed

4.2 sec in total

First Response

44 ms

Resources Loaded

3.6 sec

Page Rendered

502 ms

mapleleaffudge.com screenshot

About Website

Visit mapleleaffudge.com now to see the best up-to-date Maple Leaf Fudge content and also check out these interesting facts you probably never knew about mapleleaffudge.com

Maple Leaf Fudge® located in Niagara-on-the-Lake, offers the most amazing selection of delectable fudge flavours ever eaten. Home made fudge and brittles are made fresh daily!

Visit mapleleaffudge.com

Key Findings

We analyzed Mapleleaffudge.com page load time and found that the first response time was 44 ms and then it took 4.1 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

mapleleaffudge.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value11.2 s

0/100

25%

SI (Speed Index)

Value7.8 s

23/100

10%

TBT (Total Blocking Time)

Value1,040 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.38

27/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

mapleleaffudge.com

44 ms

mapleleaffudge.com

203 ms

wc-authorize-net-cim-checkout-block.css

58 ms

admin_icon.css

133 ms

stripe-settings.css

133 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 87% of them (75 requests) were addressed to the original Mapleleaffudge.com, 6% (5 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to . The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Mapleleaffudge.com.

Page Optimization Overview & Recommendations

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

Content Size

2.0 MB

After Optimization

1.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Mapleleaffudge.com main page is 2.0 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. 80% 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 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 72.7 kB

  • Original 89.9 kB
  • After minification 88.6 kB
  • After compression 17.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 72.7 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 3.8 kB

  • Original 1.2 MB
  • After minification 1.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. Maple Leaf Fudge images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 3.7 kB

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

CSS Optimization

-3%

Potential reduce by 15.4 kB

  • Original 542.5 kB
  • After minification 542.3 kB
  • After compression 527.2 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. Mapleleaffudge.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 54 (71%)

Requests Now

76

After Optimization

22

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

mapleleaffudge.com

mapleleaffudge.com

44 ms

mapleleaffudge.com

mapleleaffudge.com

203 ms

wc-authorize-net-cim-checkout-block.css

wc-authorize-net-cim-checkout-block.css

58 ms

admin_icon.css

admin_icon.css

133 ms

stripe-settings.css

stripe-settings.css

133 ms

sbi-styles.min.css

sbi-styles.min.css

146 ms

style.min.css

style.min.css

202 ms

trx_addons_icons-embedded.css

trx_addons_icons-embedded.css

357 ms

swiper.min.css

swiper.min.css

120 ms

magnific-popup.min.css

magnific-popup.min.css

182 ms

trx_addons.css

trx_addons.css

254 ms

trx_addons.animation.css

trx_addons.animation.css

193 ms

woocommerce-layout.css

woocommerce-layout.css

205 ms

woocommerce.css

woocommerce.css

246 ms

wt-smart-coupon-public.css

wt-smart-coupon-public.css

260 ms

sv-wc-payment-gateway-payment-form.min.css

sv-wc-payment-gateway-payment-form.min.css

267 ms

js_composer.min.css

js_composer.min.css

388 ms

css

css

39 ms

fontello-embedded.css

fontello-embedded.css

473 ms

style.css

style.css

374 ms

__styles.css

__styles.css

380 ms

__colors.css

__colors.css

400 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

413 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

434 ms

style.css

style.css

441 ms

responsive.css

responsive.css

452 ms

jquery.min.js

jquery.min.js

454 ms

jquery-migrate.min.js

jquery-migrate.min.js

469 ms

front-end.js

front-end.js

497 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

506 ms

add-to-cart.min.js

add-to-cart.min.js

508 ms

js.cookie.min.js

js.cookie.min.js

514 ms

woocommerce.min.js

woocommerce.min.js

525 ms

wt-smart-coupon-public.js

wt-smart-coupon-public.js

527 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

546 ms

wc-blocks.css

wc-blocks.css

621 ms

vc_carousel.min.css

vc_carousel.min.css

620 ms

swiper.jquery.min.js

swiper.jquery.min.js

621 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

620 ms

trx_addons.js

trx_addons.js

584 ms

jquery.payment.min.js

jquery.payment.min.js

507 ms

sv-wc-payment-gateway-payment-form.js

sv-wc-payment-gateway-payment-form.js

572 ms

wc-authorize-net-cim.min.js

wc-authorize-net-cim.min.js

573 ms

sourcebuster.min.js

sourcebuster.min.js

558 ms

order-attribution.min.js

order-attribution.min.js

521 ms

superfish.js

superfish.js

507 ms

__scripts.js

__scripts.js

500 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

587 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

516 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

506 ms

js_composer_front.min.js

js_composer_front.min.js

524 ms

cart-fragments.min.js

cart-fragments.min.js

498 ms

transition.min.js

transition.min.js

407 ms

vc_carousel.min.js

vc_carousel.min.js

439 ms

fbevents.js

fbevents.js

91 ms

sbi-sprite.png

sbi-sprite.png

316 ms

bg.jpg

bg.jpg

193 ms

mapleleaffudge_logo_withleaf.png

mapleleaffudge_logo_withleaf.png

66 ms

pumpkinspice22-scaled.jpg

pumpkinspice22-scaled.jpg

194 ms

buy3get1free-scaled.jpg

buy3get1free-scaled.jpg

211 ms

fudgepartytrays-scaled.jpg

fudgepartytrays-scaled.jpg

212 ms

mapleleaffudge.jpg

mapleleaffudge.jpg

213 ms

caramelchocolateshome.jpg

caramelchocolateshome.jpg

213 ms

brittle.jpg

brittle.jpg

213 ms

foodtrays-1.jpg

foodtrays-1.jpg

214 ms

maplesyrup.jpg

maplesyrup.jpg

214 ms

specialityteas.jpg

specialityteas.jpg

214 ms

icewineproducts.jpg

icewineproducts.jpg

215 ms

typroducts.jpg

typroducts.jpg

216 ms

ourstory2.jpg

ourstory2.jpg

216 ms

fudgespecial.jpg

fudgespecial.jpg

226 ms

maplelefwhitelogo.png

maplelefwhitelogo.png

189 ms

tDbI2oqRg1oM3QBjjcaDkOr9rAM.woff

tDbI2oqRg1oM3QBjjcaDkOr9rAM.woff

97 ms

tDbV2oqRg1oM3QBjjcaDkOJGiRD7Owc.woff

tDbV2oqRg1oM3QBjjcaDkOJGiRD7Owc.woff

108 ms

Yq6R-LCAWCX3-6Ky7FAFrO96lA.woff

Yq6R-LCAWCX3-6Ky7FAFrO96lA.woff

133 ms

tDbX2oqRg1oM3QBjjcaDkOr4lLz5CwOnTg.woff

tDbX2oqRg1oM3QBjjcaDkOr4lLz5CwOnTg.woff

154 ms

tDbK2oqRg1oM3QBjjcaDkOr4nAfcGA.woff

tDbK2oqRg1oM3QBjjcaDkOr4nAfcGA.woff

191 ms

N+6gaV3IxODy2bWFDYGFxcAlBwqBwAA

N+6gaV3IxODy2bWFDYGFxcAlBwqBwAA

28 ms

DewXAiKGIjI2Nf5AbGnRwMHAzJBRsZWJ02MTAyaIEYm7mYGDkgLD4GMIvNaRfTAaA0J5DN7rSLwQHCZmZw2ajC2BEYscGhI2Ijc4rLRjUQbxdHAwMji0NHckgESEkkEGzmYWLk0drB+L91A0vvRiYGFwAMdiP0AAA=

DewXAiKGIjI2Nf5AbGnRwMHAzJBRsZWJ02MTAyaIEYm7mYGDkgLD4GMIvNaRfTAaA0J5DN7rSLwQHCZmZw2ajC2BEYscGhI2Ijc4rLRjUQbxdHAwMji0NHckgESEkkEGzmYWLk0drB+L91A0vvRiYGFwAMdiP0AAA=

27 ms

fontello.svg

fontello.svg

336 ms

trx_addons_icons.svg

trx_addons_icons.svg

264 ms

mapleleaffudge_logo_withleaf.png

mapleleaffudge_logo_withleaf.png

161 ms

iframe_api

iframe_api

95 ms

www-widgetapi.js

www-widgetapi.js

72 ms

mapleleaffudge.com

mapleleaffudge.com

2409 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

63 ms

Accessibility Review

mapleleaffudge.com accessibility score

81

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

High

Links do not have a discernible name

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

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

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

mapleleaffudge.com SEO score

85

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

High

Tap targets are not sized appropriately

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

mapleleaffudge.com

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