Access hakunamatatawedding.com. Hakuna Matata Weddings

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

47/100

10%

LCP (Largest Contentful Paint)

Value21.0 s

0/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value1,310 ms

18/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.9 s

3/100

10%

www.hakunamatatawedding.com

55 ms

UdL4WPhKZSFmOBMK2s3ebRqPy4TZUdEhOvQ__1Pqe-bfeCJIfFHN4UJLFRbh52jhWD9uZQquZRwUZQsKw2635eb3ZRgRFQgKFy78MkG0jAFu-WsoShFGZAsude80ZkoRdhXCHKoyjamTiY8Djhy8ZYmC-Ao1Oco8if37OcBDOcu8OfG0-eBniAoydABXjWsyihmqZe80ZkoDSWmyScmDSeBRZPoRdhXCHKoDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlOeBRiA8XpWFR-emqiAUTdcS0jhNlOeBRiA8XpWFR-emqiAUTdcS0dcmXOeBDOcu8Oeyy-am0jAuyieBXjWi8ZesTdcS0jhNlOeyy-am0jAuyieBXjWi8ZesTdcS0SaBujW48Sagyjh90jhNlOeUzjhBC-eNDifUDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlOYiaikoyjamTiY8Djhy8ZYmC-Ao1OcFzdPUaiaS0jAFu-WsoShFGZAsude80Zko0ZWbCiaiaOcBDOcu8OYiaikoGjAludcBljWsyieBaZAsq-Ao1OcFzdPUaiaS0-eBniAoydABXjWsyihmqZe80ZkoDSWmyScmDSeBRZPoRdhXCiaiaO1FUiABkZWF3jAF8ShFGZAsude80ZkoRdhXKfAB3-Y4zSh80ZPJZdcmuZPuGjABDOAikdas8ShClZe8DSeUypPGHfJAaMyMMeMw6MKGHfJpaMyMMeMS6MKGHfwKXMyMgeM96MKGHfwkXMyMgeMS6MKGHfwcXMyMgeMv6MKGHfwhXMyMgegI6MTMgDd1cnMj.js

50 ms

css2

84 ms

legacy.js

56 ms

modern.js

38 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Hakunamatatawedding.com, 43% (19 requests) were made to Images.squarespace-cdn.com and 27% (12 requests) were made to Assets.squarespace.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Use.typekit.net.

Content Size

9.6 MB

After Optimization

8.9 MB

In fact, the total size of Hakunamatatawedding.com main page is 9.6 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 8.2 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 284.2 kB

Original 332.3 kB
After minification 295.7 kB
After compression 48.1 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. This page needs HTML code to be minified as it can gain 36.5 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 284.2 kB or 86% of the original size.

Image Optimization

-4%

Potential reduce by 329.2 kB

Original 8.2 MB
After minification 7.9 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. Hakuna Matata Wedding images are well optimized though.

JavaScript Optimization

-8%

Potential reduce by 86.2 kB

Original 1.1 MB
After minification 1.1 MB
After compression 973.5 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

-1%

Potential reduce by 78 B

Original 9.9 kB
After minification 9.9 kB
After compression 9.8 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. Hakunamatatawedding.com has all CSS files already compressed.

Requests Now

After Optimization

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