Tools & Wizards About Us
360player.io screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

360player.io

360player - Embed 360 degree images and videos on your website

Page Load Speed

1.7 sec in total

First Response

316 ms

Resources Loaded

1 sec

Page Rendered

326 ms

360player.io screenshot

About Website

Welcome to 360player.io homepage info - get ready to check 360 Player best content for Iran right away, or after learning these important things about 360player.io

Compatible with all kinds of 360 pictures and videos: 3D images, vehicle interiors, architecture, drone aerial photography, video game screenshots, and more. 360player.io is the most powerful platform...

Visit 360player.io

Key Findings

We analyzed 360player.io page load time and found that the first response time was 316 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

360player.io performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value3.0 s

94/100

10%

TBT (Total Blocking Time)

Value1,460 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value10.8 s

22/100

10%

Network Requests Diagram

316 ms

main.2c1646e3c7b3.css

146 ms

js

89 ms

optimize.js

86 ms

bundle.tracing.min.js

48 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 5% of them (2 requests) were addressed to the original 360player.io, 78% (32 requests) were made to Cdn.360player.io and 5% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (513 ms) relates to the external source Cdn.360player.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 74.8 kB (17%)

Content Size

435.5 kB

After Optimization

360.6 kB

  • HTML
  • Images

In fact, the total size of 360player.io main page is 435.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 20% of websites need less resources to load. Images take 375.0 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 52.8 kB

  • Original 60.5 kB
  • After minification 37.7 kB
  • After compression 7.7 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 22.8 kB, which is 38% 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 52.8 kB or 87% of the original size.

Image Optimization

-6%

Potential reduce by 22.1 kB

  • Original 375.0 kB
  • After minification 352.9 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. 360 Player images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 9 (23%)

Requests Now

40

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

316 ms

main.2c1646e3c7b3.css

main.2c1646e3c7b3.css

146 ms

js

js

89 ms

optimize.js

optimize.js

86 ms

bundle.tracing.min.js

bundle.tracing.min.js

48 ms

runtime.7954dfeb5ad3.js

runtime.7954dfeb5ad3.js

135 ms

main.f010371beaf8.js

main.f010371beaf8.js

137 ms

home.f23c25d0abb3.js

home.f23c25d0abb3.js

216 ms

embed.56b01e657b32.js

embed.56b01e657b32.js

139 ms

css2

css2

60 ms

275 ms

logo_white_background.6530e5905372.png

logo_white_background.6530e5905372.png

135 ms

honda_logo_white.3deea73d9d21.png

honda_logo_white.3deea73d9d21.png

135 ms

buzzfeed_logo_white.147ff0bf87a4.png

buzzfeed_logo_white.147ff0bf87a4.png

134 ms

intel_logo_white.966ed681aedf.png

intel_logo_white.966ed681aedf.png

88 ms

hello_logo_white.87c83c646397.png

hello_logo_white.87c83c646397.png

148 ms

anthony_skiresort_logo_white.a7881079ca5a.png

anthony_skiresort_logo_white.a7881079ca5a.png

146 ms

ucla_logo_white.e9b2aa7a869b.png

ucla_logo_white.e9b2aa7a869b.png

176 ms

upload.aaacd131829c.png

upload.aaacd131829c.png

182 ms

share.c39c4d202c5a.png

share.c39c4d202c5a.png

182 ms

embed.e48cdd6f8a6c.png

embed.e48cdd6f8a6c.png

184 ms

plume.92f88a4cd285.png

plume.92f88a4cd285.png

242 ms

device.39a084b60091.png

device.39a084b60091.png

237 ms

storage.5091519d2bc6.png

storage.5091519d2bc6.png

260 ms

whitelabel.8c0631e47e63.png

whitelabel.8c0631e47e63.png

272 ms

878652c7-1aed-43b4-9222-33b2350d4ac4.jpeg

878652c7-1aed-43b4-9222-33b2350d4ac4.jpeg

185 ms

1c3ddb07-46fe-4f3c-87e9-22b1dc5fcdbe.jpeg

1c3ddb07-46fe-4f3c-87e9-22b1dc5fcdbe.jpeg

367 ms

689c8a39-426c-460d-8786-13483ceeee9f.jpeg

689c8a39-426c-460d-8786-13483ceeee9f.jpeg

188 ms

145d61f85bce985407b3aac7e3f5f35a.jpg

145d61f85bce985407b3aac7e3f5f35a.jpg

348 ms

2cb7badf1c5ceb3cb2cc7cb48758509f.jpg

2cb7badf1c5ceb3cb2cc7cb48758509f.jpg

332 ms

f702b6acfdcf31e522aaec6d520658b4.jpg

f702b6acfdcf31e522aaec6d520658b4.jpg

337 ms

aa9a3a39dd350b010ee897fac234c9d8.jpg

aa9a3a39dd350b010ee897fac234c9d8.jpg

359 ms

31a572be0a7df9b4daae58cc2d8b4929.jpg

31a572be0a7df9b4daae58cc2d8b4929.jpg

415 ms

a6d58ddd6907d94d2eb0aa4cc371d695.jpg

a6d58ddd6907d94d2eb0aa4cc371d695.jpg

513 ms

social_linkedin.8f0610805d25.png

social_linkedin.8f0610805d25.png

422 ms

social_github.d56df49a807a.png

social_github.d56df49a807a.png

449 ms

font

font

18 ms

js

js

47 ms

bundle.tracing.min.js

bundle.tracing.min.js

8 ms

player.b89e9a9cf4cd.js

player.b89e9a9cf4cd.js

223 ms

logo_player@2x.61437c7cea95.webp

logo_player@2x.61437c7cea95.webp

143 ms

Accessibility Review

360player.io accessibility score

79

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

360player.io best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

360player.io SEO score

100

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

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 360player.io 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 360player.io 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

360player.io

Open Graph description is not detected on the main page of 360 Player. 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: