Access 52main.com. 52 Main | Tapas...small plates of savory mouthfuls meant to be enjoyed

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value9.4 s

0/100

25%

SI (Speed Index)

Value14.1 s

1/100

10%

TBT (Total Blocking Time)

Value2,870 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.066

97/100

15%

TTI (Time to Interactive)

Value18.7 s

3/100

10%

52main.com

49 ms

www.52main.com

76 ms

www.abouquetoflove.com

2240 ms

gtm.js

84 ms

gtm.js

138 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original 52main.com, 47% (28 requests) were made to Img-1-12.rapidflarecdn.net and 32% (19 requests) were made to Txt-1-12.rapidflarecdn.net. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Abouquetoflove.com.

Content Size

1.6 MB

After Optimization

520.2 kB

In fact, the total size of 52main.com main page is 1.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. 50% of websites need less resources to load. HTML takes 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 926.5 kB

Original 1.0 MB
After minification 1.0 MB
After compression 84.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 926.5 kB or 92% of the original size.

Image Optimization

-22%

Potential reduce by 56.0 kB

Original 256.3 kB
After minification 200.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. Obviously, 52 Main needs image optimization as it can save up to 56.0 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-20%

Potential reduce by 50.8 kB

Original 249.7 kB
After minification 249.5 kB
After compression 198.9 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 50.8 kB or 20% of the original size.

CSS Optimization

-43%

Potential reduce by 27.5 kB

Original 64.4 kB
After minification 64.3 kB
After compression 36.9 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. 52main.com needs all CSS files to be minified and compressed as it can save up to 27.5 kB or 43% of the original size.

Requests Now

After Optimization

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