Tools & Wizards About Us
imaterialise.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

imaterialise.com

Online 3D Printing Service | i.materialise

Page Load Speed

2 sec in total

First Response

16 ms

Resources Loaded

1 sec

Page Rendered

971 ms

imaterialise.com screenshot

About Website

Welcome to imaterialise.com homepage info - get ready to check I Materialise best content right away, or after learning these important things about imaterialise.com

i.materialise is an online 3D printing service, community and marketplace. Upload your 3D design and choose from over 100 different finishes and materials.

Visit imaterialise.com

Key Findings

We analyzed Imaterialise.com page load time and found that the first response time was 16 ms and then it took 2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

imaterialise.com performance score

0

Network Requests Diagram

imaterialise.com

16 ms

i.materialise.com

166 ms

evf1xlh.js

40 ms

jquery.lightbox-0.5.css

11 ms

jquery-ui-1.7.custom.css

27 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Imaterialise.com, 50% (26 requests) were made to I.materialise.com and 13% (7 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (371 ms) relates to the external source T.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 718.8 kB (52%)

Content Size

1.4 MB

After Optimization

652.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Imaterialise.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. 70% of websites need less resources to load. CSS take 517.0 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 107.3 kB

  • Original 121.4 kB
  • After minification 74.8 kB
  • After compression 14.1 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 46.6 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 107.3 kB or 88% of the original size.

Image Optimization

-2%

Potential reduce by 8.1 kB

  • Original 355.6 kB
  • After minification 347.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. I Materialise images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 284.2 kB

  • Original 377.2 kB
  • After minification 377.2 kB
  • After compression 93.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 284.2 kB or 75% of the original size.

CSS Optimization

-62%

Potential reduce by 319.2 kB

  • Original 517.0 kB
  • After minification 511.4 kB
  • After compression 197.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. Imaterialise.com needs all CSS files to be minified and compressed as it can save up to 319.2 kB or 62% of the original size.

Requests Breakdown

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

Requests Now

42

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 42 CSS, Javascripts, AJAX and image requests in order to completely render the main page of I Materialise. 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 from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

imaterialise.com

imaterialise.com

16 ms

i.materialise.com

i.materialise.com

166 ms

evf1xlh.js

evf1xlh.js

40 ms

jquery.lightbox-0.5.css

jquery.lightbox-0.5.css

11 ms

jquery-ui-1.7.custom.css

jquery-ui-1.7.custom.css

27 ms

UI-kit-4mainSite.css

UI-kit-4mainSite.css

87 ms

main-home-page.css

main-home-page.css

34 ms

common

common

56 ms

all

all

54 ms

all

all

32 ms

all

all

33 ms

all

all

49 ms

all

all

50 ms

fbds.js

fbds.js

232 ms

goal.min.js

goal.min.js

357 ms

oct.js

oct.js

234 ms

gtm.js

gtm.js

362 ms

svg-layout-images.svg

svg-layout-images.svg

146 ms

logo.png

logo.png

146 ms

logo-white.png

logo-white.png

37 ms

s-getting-started-bg.jpg

s-getting-started-bg.jpg

149 ms

s-how-to-order-steps.png

s-how-to-order-steps.png

149 ms

s-why-order-cards-bg.jpg

s-why-order-cards-bg.jpg

149 ms

s-upload-and-order.png

s-upload-and-order.png

157 ms

s-3d-printing-materials-cards-bg.jpg

s-3d-printing-materials-cards-bg.jpg

157 ms

trusted-partner-bg.png

trusted-partner-bg.png

156 ms

materialise-logo.png

materialise-logo.png

156 ms

d

d

32 ms

d

d

156 ms

d

d

156 ms

d

d

156 ms

d

d

152 ms

140 ms

adsct

adsct

371 ms

CheckCookies

CheckCookies

100 ms

usercart

usercart

86 ms

adsct

adsct

348 ms

default_cart_preview.png

default_cart_preview.png

34 ms

d

d

24 ms

p.gif

p.gif

38 ms

hotjar-497955.js

hotjar-497955.js

107 ms

analytics.js

analytics.js

32 ms

js

js

49 ms

modules-f524bccd859bfc7e394e1123f7f90405.js

modules-f524bccd859bfc7e394e1123f7f90405.js

58 ms

rcj-99d43ead6bdf30da8ed5ffcb4f17100c.html

rcj-99d43ead6bdf30da8ed5ffcb4f17100c.html

75 ms

s-why-order-cards-bg.jpg

s-why-order-cards-bg.jpg

47 ms

collect

collect

39 ms

collect

collect

34 ms

collect

collect

63 ms

ga-audiences

ga-audiences

40 ms

s-getting-started-bg.jpg

s-getting-started-bg.jpg

30 ms

26 ms

SEO Factors

imaterialise.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imaterialise.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 Imaterialise.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

imaterialise.com

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