Access instax.com. instax™

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

59/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value780 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0.087

93/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

instax.com

478 ms

instax.com

596 ms

gtm.js

69 ms

css2

46 ms

reset.css

155 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 88% of them (52 requests) were addressed to the original Instax.com, 5% (3 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Instax.com.

Content Size

10.1 MB

After Optimization

7.1 MB

In fact, the total size of Instax.com main page is 10.1 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. 55% of websites need less resources to load. Images take 9.8 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 35.2 kB

Original 40.8 kB
After minification 27.3 kB
After compression 5.6 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 13.5 kB, which is 33% 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 35.2 kB or 86% of the original size.

Image Optimization

-28%

Potential reduce by 2.8 MB

Original 9.8 MB
After minification 7.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. Obviously, Instax needs image optimization as it can save up to 2.8 MB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 88.7 kB

Original 137.0 kB
After minification 99.3 kB
After compression 48.3 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 88.7 kB or 65% of the original size.

CSS Optimization

-91%

Potential reduce by 79.9 kB

Original 87.7 kB
After minification 66.1 kB
After compression 7.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. Instax.com needs all CSS files to be minified and compressed as it can save up to 79.9 kB or 91% 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 Instax. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.