Tools & Wizards About Us
insta360.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

insta360.com

Insta360 | Action Cameras | 360 Cameras | VR Cameras

Page Load Speed

3.7 sec in total

First Response

164 ms

Resources Loaded

1.1 sec

Page Rendered

2.4 sec

insta360.com screenshot

About Website

Welcome to insta360.com homepage info - get ready to check Insta360 best content for United States right away, or after learning these important things about insta360.com

Building better cameras. Discover our leading line of shooters for athletes, creators and VR pros.

Visit insta360.com

Key Findings

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

insta360.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

79/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value10.2 s

9/100

10%

TBT (Total Blocking Time)

Value1,260 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.019

100/100

15%

TTI (Time to Interactive)

Value9.7 s

28/100

10%

Network Requests Diagram

insta360.com

164 ms

www.insta360.com

365 ms

3e44d7f615ed53bf.css

21 ms

36e29285a3e44c46.css

35 ms

cc7e0d700e4dbdd0.css

31 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 34% of them (29 requests) were addressed to the original Insta360.com, 48% (41 requests) were made to Res.insta360.com and 12% (10 requests) were made to Static.insta360.com. The less responsive or slowest element that took the longest time to load (553 ms) relates to the external source Retcode.alicdn.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 32.4 kB (2%)

Content Size

1.9 MB

After Optimization

1.9 MB

  • Images
  • JavaScript
  • CSS

In fact, the total size of Insta360.com main page is 1.9 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. 80% 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 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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 web page is already compressed.

Image Optimization

-0%

Potential reduce by 6 B

  • Original 1.5 MB
  • After minification 1.5 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. Insta360 images are well optimized though.

JavaScript Optimization

-10%

Potential reduce by 32.3 kB

  • Original 338.7 kB
  • After minification 338.7 kB
  • After compression 306.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

-0%

Potential reduce by 78 B

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

Requests Breakdown

Number of requests can be reduced by 51 (61%)

Requests Now

84

After Optimization

33

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

insta360.com

insta360.com

164 ms

www.insta360.com

www.insta360.com

365 ms

3e44d7f615ed53bf.css

3e44d7f615ed53bf.css

21 ms

36e29285a3e44c46.css

36e29285a3e44c46.css

35 ms

cc7e0d700e4dbdd0.css

cc7e0d700e4dbdd0.css

31 ms

9eda7ced583d3100.css

9eda7ced583d3100.css

29 ms

f2864859c44e14c2.css

f2864859c44e14c2.css

33 ms

55b0213d5f827ecf.css

55b0213d5f827ecf.css

27 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

73 ms

40526-8a60c90880c26964.js

40526-8a60c90880c26964.js

72 ms

74529.e77daf019a1f2623.js

74529.e77daf019a1f2623.js

91 ms

53266.ff52480b6ae96d53.js

53266.ff52480b6ae96d53.js

92 ms

65681.3adba146620c1a08.js

65681.3adba146620c1a08.js

94 ms

53657.29a4a2b005edb66f.js

53657.29a4a2b005edb66f.js

94 ms

3841.008c0bfa09adf8b4.js

3841.008c0bfa09adf8b4.js

97 ms

84925.f6e5c6339bff7394.js

84925.f6e5c6339bff7394.js

105 ms

webpack-6ec1e140ca033678.js

webpack-6ec1e140ca033678.js

105 ms

framework-c7da159cbcd5b2e0.js

framework-c7da159cbcd5b2e0.js

105 ms

main-736f18c955560505.js

main-736f18c955560505.js

150 ms

_app-4e39c5f1d8b37bb2.js

_app-4e39c5f1d8b37bb2.js

112 ms

b637e9a5-9ffc793c3942dd05.js

b637e9a5-9ffc793c3942dd05.js

407 ms

67354-6eb3325e8630193d.js

67354-6eb3325e8630193d.js

405 ms

98595-ad1c61b460e57b1c.js

98595-ad1c61b460e57b1c.js

407 ms

18433-070b9e246a735bf1.js

18433-070b9e246a735bf1.js

407 ms

69731-8c0c8355dce9f9e0.js

69731-8c0c8355dce9f9e0.js

405 ms

49091-9cc0523f28a38a18.js

49091-9cc0523f28a38a18.js

412 ms

desktop-373b5b0dd9f86589.js

desktop-373b5b0dd9f86589.js

472 ms

_buildManifest.js

_buildManifest.js

510 ms

_ssgManifest.js

_ssgManifest.js

498 ms

js

js

109 ms

beacon.min.js

beacon.min.js

108 ms

bl.js

bl.js

553 ms

logo-black.svg

logo-black.svg

372 ms

en_us_2x.png

en_us_2x.png

370 ms

analytics.js

analytics.js

362 ms

fbevents.js

fbevents.js

361 ms

ic-close.svg

ic-close.svg

360 ms

ic-arrow-down.svg

ic-arrow-down.svg

358 ms

real-estate.jpg

real-estate.jpg

358 ms

NavWinterSports.jpg

NavWinterSports.jpg

409 ms

NavMotorcycle.jpg

NavMotorcycle.jpg

438 ms

NavBiking.jpg

NavBiking.jpg

434 ms

NavWaterSports.jpg

NavWaterSports.jpg

443 ms

ic-left.svg

ic-left.svg

438 ms

ic-right.svg

ic-right.svg

440 ms

ic-left-white.svg

ic-left-white.svg

444 ms

ic-right-white.svg

ic-right-white.svg

445 ms

ic-arrow-black.svg

ic-arrow-black.svg

454 ms

WinterSportsMO.jpg

WinterSportsMO.jpg

454 ms

MotorcycleMO.jpg

MotorcycleMO.jpg

456 ms

BikingMO.jpg

BikingMO.jpg

457 ms

WaterSportsMO.jpg

WaterSportsMO.jpg

458 ms

ndnp.png

ndnp.png

459 ms

ndnp-mob.png

ndnp-mob.png

460 ms

AiWarp-PC.jpg

AiWarp-PC.jpg

475 ms

AiWarp-MO.jpg

AiWarp-MO.jpg

476 ms

Insta360Rising-PC.jpg

Insta360Rising-PC.jpg

484 ms

Insta360Rising.jpg

Insta360Rising.jpg

483 ms

fast-company.jpg

fast-company.jpg

481 ms

fast-company-mob.jpg

fast-company-mob.jpg

479 ms

team-insta360.jpg

team-insta360.jpg

480 ms

team-insta360-mob.jpg

team-insta360-mob.jpg

479 ms

vision-pro.jpg

vision-pro.jpg

499 ms

vision-pro-mob.jpg

vision-pro-mob.jpg

500 ms

ic_black.svg

ic_black.svg

497 ms

Rectangle%205%20(Stroke).svg

Rectangle%205%20(Stroke).svg

497 ms

1006.svg

1006.svg

493 ms

icon_tiktok_hover.svg

icon_tiktok_hover.svg

500 ms

10001-(1)%20(1).svg

10001-(1)%20(1).svg

510 ms

icon_youtube_hover.svg

icon_youtube_hover.svg

512 ms

icon-x.svg

icon-x.svg

513 ms

de_de_2x.png

de_de_2x.png

352 ms

zh_cn_2x.png

zh_cn_2x.png

349 ms

zh_tw_2x.png

zh_tw_2x.png

353 ms

ja_jp_2x.png

ja_jp_2x.png

404 ms

es_es_2x.png

es_es_2x.png

430 ms

ko_kr_2x.png

ko_kr_2x.png

356 ms

fr_fr_2x.png

fr_fr_2x.png

430 ms

it_it_2x.png

it_it_2x.png

432 ms

ru_ru_2x.png

ru_ru_2x.png

438 ms

icon-x-hover.svg

icon-x-hover.svg

177 ms

10005-(1)%20(1).svg

10005-(1)%20(1).svg

160 ms

icon_fb_hover.svg

icon_fb_hover.svg

161 ms

10003%20(1).svg

10003%20(1).svg

172 ms

451591722489720

451591722489720

64 ms

icon_ig_hover.svg

icon_ig_hover.svg

127 ms

Accessibility Review

insta360.com accessibility score

88

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

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

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

insta360.com SEO score

85

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Insta360.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Insta360.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

insta360.com

Open Graph description is not detected on the main page of Insta360. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: