Tools & Wizards About Us
babylonjs-playground.azurewebsites.net screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

Page Load Speed

4.9 sec in total

First Response

267 ms

Resources Loaded

4.4 sec

Page Rendered

156 ms

babylonjs-playground.azurewebsites.net screenshot

About Website

Welcome to babylonjs-playground.azurewebsites.net homepage info - get ready to check Babylon Js Playground Azurewebsites best content for United States right away, or after learning these important things about babylonjs-playground.azurewebsites.net

Visit babylonjs-playground.azurewebsites.net

Key Findings

We analyzed Babylonjs-playground.azurewebsites.net page load time and found that the first response time was 267 ms and then it took 4.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

babylonjs-playground.azurewebsites.net performance score

0

Network Requests Diagram

babylonjs-playground.azurewebsites.net

267 ms

poly2tri.js

548 ms

dat.gui.min.js

1222 ms

splitbox.css

751 ms

x-tag-core.min.js

1441 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 51% of them (32 requests) were addressed to the original Babylonjs-playground.azurewebsites.net, 41% (26 requests) were made to Yoda.blob.core.windows.net and 6% (4 requests) were made to Babylonjs.com. The less responsive or slowest element that took the longest time to load (3.3 sec) relates to the external source Babylonjs.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.9 MB (80%)

Content Size

2.3 MB

After Optimization

479.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Babylonjs-playground.azurewebsites.net main page is 2.3 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. 45% of websites need less resources to load. Javascripts take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 38.9 kB

  • Original 46.4 kB
  • After minification 45.4 kB
  • After compression 7.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 38.9 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 53 B

  • Original 891 B
  • After minification 838 B

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. Babylon Js Playground Azurewebsites images are well optimized though.

JavaScript Optimization

-79%

Potential reduce by 1.6 MB

  • Original 2.1 MB
  • After minification 1.8 MB
  • After compression 435.9 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 1.6 MB or 79% of the original size.

CSS Optimization

-85%

Potential reduce by 200.8 kB

  • Original 235.6 kB
  • After minification 209.1 kB
  • After compression 34.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. Babylonjs-playground.azurewebsites.net needs all CSS files to be minified and compressed as it can save up to 200.8 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 54 (87%)

Requests Now

62

After Optimization

8

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

babylonjs-playground.azurewebsites.net

babylonjs-playground.azurewebsites.net

267 ms

poly2tri.js

poly2tri.js

548 ms

dat.gui.min.js

dat.gui.min.js

1222 ms

splitbox.css

splitbox.css

751 ms

x-tag-core.min.js

x-tag-core.min.js

1441 ms

splitbox.js

splitbox.js

581 ms

jszip.min.js

jszip.min.js

1360 ms

fileSaver.js

fileSaver.js

802 ms

bootstrap.min.css

bootstrap.min.css

1495 ms

editor.main.css

editor.main.css

423 ms

vs-theme.css

vs-theme.css

235 ms

loader.js

loader.js

333 ms

editor.main.nls.js

editor.main.nls.js

235 ms

editor.main.js

editor.main.js

861 ms

javascript.js

javascript.js

431 ms

css.js

css.js

408 ms

html.js

html.js

411 ms

cannon.js

cannon.js

2029 ms

Oimo.js

Oimo.js

1978 ms

babylon.js

babylon.js

3329 ms

babylon.fireMaterial.min.js

babylon.fireMaterial.min.js

1098 ms

babylon.waterMaterial.min.js

babylon.waterMaterial.min.js

1274 ms

babylon.lavaMaterial.min.js

babylon.lavaMaterial.min.js

1227 ms

babylon.normalMaterial.min.js

babylon.normalMaterial.min.js

1468 ms

babylon.pbrMaterial.min.js

babylon.pbrMaterial.min.js

1680 ms

babylon.skyMaterial.min.js

babylon.skyMaterial.min.js

1427 ms

babylon.triPlanarMaterial.min.js

babylon.triPlanarMaterial.min.js

1682 ms

babylon.terrainMaterial.min.js

babylon.terrainMaterial.min.js

1680 ms

babylon.gradientMaterial.min.js

babylon.gradientMaterial.min.js

1679 ms

babylon.furMaterial.min.js

babylon.furMaterial.min.js

1681 ms

babylon.gridMaterial.min.js

babylon.gridMaterial.min.js

1680 ms

babylon.brickProceduralTexture.min.js

babylon.brickProceduralTexture.min.js

1727 ms

babylon.cloudProceduralTexture.min.js

babylon.cloudProceduralTexture.min.js

1711 ms

babylon.fireProceduralTexture.min.js

babylon.fireProceduralTexture.min.js

1728 ms

babylon.grassProceduralTexture.min.js

babylon.grassProceduralTexture.min.js

1755 ms

babylon.marbleProceduralTexture.min.js

babylon.marbleProceduralTexture.min.js

1723 ms

babylon.roadProceduralTexture.min.js

babylon.roadProceduralTexture.min.js

1805 ms

babylon.starfieldProceduralTexture.min.js

babylon.starfieldProceduralTexture.min.js

1744 ms

babylon.woodProceduralTexture.min.js

babylon.woodProceduralTexture.min.js

1807 ms

index.css

index.css

1945 ms

jquery.js

jquery.js

8 ms

bootstrap.min.js

bootstrap.min.js

1946 ms

index.js

index.js

1973 ms

vsxml.js

vsxml.js

92 ms

typescriptServices.js

typescriptServices.js

536 ms

projectResolver.js

projectResolver.js

107 ms

scripts.txt

scripts.txt

30 ms

arrow-left.png

arrow-left.png

115 ms

arrow-right.png

arrow-right.png

116 ms

arrow-up.png

arrow-up.png

114 ms

arrow-down.png

arrow-down.png

444 ms

expando-collapsed.png

expando-collapsed.png

103 ms

case-sensitive.svg

case-sensitive.svg

131 ms

whole-word.svg

whole-word.svg

223 ms

regex.svg

regex.svg

219 ms

previous.svg

previous.svg

204 ms

next.svg

next.svg

207 ms

cancelSelectionFind.svg

cancelSelectionFind.svg

220 ms

close.svg

close.svg

296 ms

lightbulp.svg

lightbulp.svg

298 ms

basic%20scene.js

basic%20scene.js

286 ms

workerMainCompatibility.html

workerMainCompatibility.html

131 ms

workerServer.js

workerServer.js

93 ms

SEO Factors

babylonjs-playground.azurewebsites.net SEO score

0

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 Babylonjs-playground.azurewebsites.net 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 Babylonjs-playground.azurewebsites.net 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

babylonjs-playground.azurewebsites.net

Open Graph description is not detected on the main page of Babylon Js Playground Azurewebsites. 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: