Tools & Wizards About Us
in1case.com screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

in1case.com

Demand more from your case

Page Load Speed

3.5 sec in total

First Response

76 ms

Resources Loaded

2.6 sec

Page Rendered

856 ms

in1case.com screenshot

About Website

Visit in1case.com now to see the best up-to-date In1 Case content for United States and also check out these interesting facts you probably never knew about in1case.com

IN1 is an innovative phone case manufacturer with industry changing design concepts. IIPT, Nano Shiled.

Visit in1case.com

Key Findings

We analyzed In1case.com page load time and found that the first response time was 76 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

in1case.com performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value8,350 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value29.6 s

0/100

10%

Network Requests Diagram

www.in1case.com

76 ms

minified.js

31 ms

focus-within-polyfill.js

61 ms

polyfill.min.js

977 ms

thunderbolt-commons.6fb81d6e.bundle.min.js

53 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original In1case.com, 26% (15 requests) were made to Static.parastorage.com and 24% (14 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) relates to the external source Youtube.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 657.4 kB (46%)

Content Size

1.4 MB

After Optimization

762.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of In1case.com main page is 1.4 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. Only a small number of websites need less resources to load. Javascripts take 705.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 429.4 kB

  • Original 546.0 kB
  • After minification 544.4 kB
  • After compression 116.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. 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 429.4 kB or 79% of the original size.

Image Optimization

-6%

Potential reduce by 2.8 kB

  • Original 50.2 kB
  • After minification 47.4 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. In1 Case images are well optimized though.

JavaScript Optimization

-32%

Potential reduce by 225.2 kB

  • Original 705.2 kB
  • After minification 705.2 kB
  • After compression 480.0 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 225.2 kB or 32% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 118.7 kB
  • After minification 118.7 kB
  • After compression 118.7 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. In1case.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 15 (38%)

Requests Now

40

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.in1case.com

www.in1case.com

76 ms

minified.js

minified.js

31 ms

focus-within-polyfill.js

focus-within-polyfill.js

61 ms

polyfill.min.js

polyfill.min.js

977 ms

thunderbolt-commons.6fb81d6e.bundle.min.js

thunderbolt-commons.6fb81d6e.bundle.min.js

53 ms

main.e99c0319.bundle.min.js

main.e99c0319.bundle.min.js

59 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

54 ms

lodash.min.js

lodash.min.js

59 ms

react.production.min.js

react.production.min.js

54 ms

react-dom.production.min.js

react-dom.production.min.js

57 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

56 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

57 ms

f3b50b_10764c1c83764928812d1a223d7fe2acf000.jpg

f3b50b_10764c1c83764928812d1a223d7fe2acf000.jpg

36 ms

f3b50b_bd158aec772944d1a0d2d59914538c26~mv2.png

f3b50b_bd158aec772944d1a0d2d59914538c26~mv2.png

191 ms

f3b50b_fc884c4d5fd4401d887ff2d6735f62a7~mv2_d_2803_3502_s_4_2.png

f3b50b_fc884c4d5fd4401d887ff2d6735f62a7~mv2_d_2803_3502_s_4_2.png

206 ms

f3b50b_e983ab62a3a743cd83b2e64efc5f3a67~mv2_d_3889_6667_s_4_2.png

f3b50b_e983ab62a3a743cd83b2e64efc5f3a67~mv2_d_3889_6667_s_4_2.png

205 ms

f3b50b_43d2a8977535445083735ea07b853904~mv2.jpg

f3b50b_43d2a8977535445083735ea07b853904~mv2.jpg

204 ms

f3b50b_2e043502b1534f988c9a06b133d50643~mv2_d_4350_2850_s_4_2.jpg

f3b50b_2e043502b1534f988c9a06b133d50643~mv2_d_4350_2850_s_4_2.jpg

206 ms

f3b50b_cbfce2373f48439fb955621d1a36dab4~mv2.jpg

f3b50b_cbfce2373f48439fb955621d1a36dab4~mv2.jpg

205 ms

f3b50b_168f2c3306f74511af34c2a576511794~mv2_d_6405_6471_s_4_2.png

f3b50b_168f2c3306f74511af34c2a576511794~mv2_d_6405_6471_s_4_2.png

206 ms

f3b50b_27e642148873487db8bd29bbc11eb1ca~mv2_d_4350_2850_s_4_2.jpg

f3b50b_27e642148873487db8bd29bbc11eb1ca~mv2_d_4350_2850_s_4_2.jpg

242 ms

f3b50b_fb2482f1b6f3446aae84364752356569~mv2.jpg

f3b50b_fb2482f1b6f3446aae84364752356569~mv2.jpg

241 ms

f3b50b_152a73d6dd084ca697a70603c1d49a81~mv2_d_2667_2667_s_4_2.jpg

f3b50b_152a73d6dd084ca697a70603c1d49a81~mv2_d_2667_2667_s_4_2.jpg

242 ms

f3b50b_ab945b91b8754af9aace57ea78f6d4d2~mv2.jpg

f3b50b_ab945b91b8754af9aace57ea78f6d4d2~mv2.jpg

241 ms

f3b50b_3947b05b94ba4a2ebf7132e3db964e2a~mv2_d_3472_3472_s_4_2.png

f3b50b_3947b05b94ba4a2ebf7132e3db964e2a~mv2_d_3472_3472_s_4_2.png

240 ms

f3b50b_910dd97a33f24be1b01b976a4808ec66~mv2_d_1667_2084_s_2.jpg

f3b50b_910dd97a33f24be1b01b976a4808ec66~mv2_d_1667_2084_s_2.jpg

240 ms

Cdea0APVFic

Cdea0APVFic

318 ms

08VKjiD4qWk

08VKjiD4qWk

408 ms

tVun9wpvr8Y

tVun9wpvr8Y

413 ms

ZeBOQSKD6Mk

ZeBOQSKD6Mk

450 ms

hUlEh2OuRZo

hUlEh2OuRZo

398 ms

U6JOxzUUBg4

U6JOxzUUBg4

448 ms

VGRMq-426m4

VGRMq-426m4

596 ms

H9kPCEhM3R0

H9kPCEhM3R0

1238 ms

bundle.min.js

bundle.min.js

123 ms

80de9d5d-ab5f-40ce-911b-104e51e93d7c.woff

80de9d5d-ab5f-40ce-911b-104e51e93d7c.woff

18 ms

4021a3b9-f782-438b-aeb4-c008109a8b64.woff

4021a3b9-f782-438b-aeb4-c008109a8b64.woff

19 ms

b56b944e-bbe0-4450-a241-de2125d3e682.woff

b56b944e-bbe0-4450-a241-de2125d3e682.woff

42 ms

6f8d1983-4d34-4fa4-9110-988f6c495757.woff

6f8d1983-4d34-4fa4-9110-988f6c495757.woff

16 ms

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

908c4810-64db-4b46-bb8e-823eb41f68c0.woff

17 ms

130 ms

123 ms

122 ms

118 ms

119 ms

112 ms

153 ms

151 ms

148 ms

148 ms

179 ms

148 ms

www-player.css

www-player.css

110 ms

www-embed-player.js

www-embed-player.js

134 ms

base.js

base.js

296 ms

www-player.css

www-player.css

95 ms

www-embed-player.js

www-embed-player.js

141 ms

base.js

base.js

516 ms

Accessibility Review

in1case.com accessibility score

89

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

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.

Best Practices

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

High

Page has valid source maps

SEO Factors

in1case.com SEO score

99

Search Engine Optimization Advices

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

in1case.com

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