Tools & Wizards About Us
instax.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

instax.com

instax™ | FUJIFILM

Page Load Speed

3.9 sec in total

First Response

478 ms

Resources Loaded

3.1 sec

Page Rendered

326 ms

instax.com screenshot

About Website

Click here to check amazing Instax content for United States. Otherwise, check out these important facts you probably never knew about instax.com

Global branding site of FUJIFILM's instant camera instax series. This site will introduce the various appealing features of instax™.

Visit instax.com

Key Findings

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

instax.com performance score

47

Measured Metrics

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%

Network Requests Diagram

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.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.0 MB (29%)

Content Size

10.1 MB

After Optimization

7.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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 Breakdown

Number of requests can be reduced by 12 (22%)

Requests Now

54

After Optimization

42

  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

instax.com

instax.com

478 ms

instax.com

instax.com

596 ms

gtm.js

gtm.js

69 ms

css2

css2

46 ms

reset.css

reset.css

155 ms

base.css

base.css

303 ms

slick.css

slick.css

431 ms

slick-theme.css

slick-theme.css

433 ms

top.css

top.css

434 ms

jquery.min.js

jquery.min.js

29 ms

slick.js

slick.js

579 ms

common.js

common.js

452 ms

covervid.js

covervid.js

452 ms

top.js

top.js

570 ms

footer.css

footer.css

575 ms

logo_01.svg

logo_01.svg

153 ms

logo_02.svg

logo_02.svg

149 ms

switch.svg

switch.svg

152 ms

close.svg

close.svg

144 ms

arrow_01.svg

arrow_01.svg

147 ms

navi_image_20.png

navi_image_20.png

146 ms

navi_image_02.png

navi_image_02.png

288 ms

navi_image_instax-mini99.png

navi_image_instax-mini99.png

291 ms

navi_image_22.png

navi_image_22.png

292 ms

navi_instax-miniLiPlay.png

navi_instax-miniLiPlay.png

290 ms

navi_image_21.png

navi_image_21.png

293 ms

navi_image_08.png

navi_image_08.png

295 ms

navi_image_instax-wide400.png

navi_image_instax-wide400.png

428 ms

navi_image_instax-pal.png

navi_image_instax-pal.png

435 ms

navi_image_17.png

navi_image_17.png

435 ms

navi_image_19.png

navi_image_19.png

434 ms

navi_image_18.png

navi_image_18.png

440 ms

navi_image_15.png

navi_image_15.png

442 ms

global_icon_02.svg

global_icon_02.svg

571 ms

image_01.png

image_01.png

1004 ms

image_02.png

image_02.png

859 ms

image_02-sp.png

image_02-sp.png

865 ms

image_03.png

image_03.png

876 ms

image_03-sp.png

image_03-sp.png

878 ms

image_04.png

image_04.png

1133 ms

slider_wide400.png

slider_wide400.png

1004 ms

slider_wide400-sp.png

slider_wide400-sp.png

1014 ms

slider_miniLiPlay.jpg

slider_miniLiPlay.jpg

1024 ms

slider_miniLiPlay-sp.jpg

slider_miniLiPlay-sp.jpg

1027 ms

slider_app.jpg

slider_app.jpg

1151 ms

slider_app-sp.jpg

slider_app-sp.jpg

1150 ms

slider_03.jpg

slider_03.jpg

1159 ms

slider_03-sp.jpg

slider_03-sp.jpg

1172 ms

image_05_ov.png

image_05_ov.png

1174 ms

image_05.png

image_05.png

1280 ms

image_05-sp.png

image_05-sp.png

1211 ms

KFOmCnqEu92Fr1Me5g.woff

KFOmCnqEu92Fr1Me5g.woff

18 ms

KFOlCnqEu92Fr1MmWUlvAA.woff

KFOlCnqEu92Fr1MmWUlvAA.woff

29 ms

KFOlCnqEu92Fr1MmYUtvAA.woff

KFOlCnqEu92Fr1MmYUtvAA.woff

30 ms

image_06_ov.png

image_06_ov.png

1156 ms

image_06.png

image_06.png

1305 ms

image_06-sp.png

image_06-sp.png

1320 ms

footer_logo_01.svg

footer_logo_01.svg

1176 ms

mieruca-hm.js

mieruca-hm.js

59 ms

Accessibility Review

instax.com accessibility score

87

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

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

instax.com SEO score

90

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

    JA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Instax.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Japanese language. Our system also found out that Instax.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

instax.com

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