2.1 sec in total
58 ms
1.7 sec
292 ms
Welcome to additive.works homepage info - get ready to check Additive best content right away, or after learning these important things about additive.works
Metal Additive Manufacturing Software | Developed by Oqton | Additive Manufacturing Simulation Software
Visit additive.worksWe analyzed Additive.works page load time and found that the first response time was 58 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 40% of websites can load faster.
additive.works performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value10.0 s
0/100
25%
Value5.7 s
52/100
10%
Value1,520 ms
13/100
30%
Value0
100/100
15%
Value25.6 s
0/100
10%
58 ms
321 ms
175 ms
10 ms
113 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Additive.works, 80% (33 requests) were made to Oqton.com and 5% (2 requests) were made to W.chatlio.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Oqton.com.
Page size can be reduced by 1.0 MB (52%)
2.0 MB
956.7 kB
In fact, the total size of Additive.works main page is 2.0 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. 50% of websites need less resources to load. Javascripts take 829.3 kB which makes up the majority of the site volume.
Potential reduce by 298.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 298.6 kB or 75% of the original size.
Potential reduce by 159.1 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. Obviously, Additive needs image optimization as it can save up to 159.1 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 573.3 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 573.3 kB or 69% of the original size.
Number of requests can be reduced by 12 (39%)
31
19
The browser has sent 31 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Additive. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
additive.works
58 ms
321 ms
gtm.js
175 ms
chatlio.js
10 ms
v4.js
113 ms
ruler_analytics.js
41 ms
polyfill-6bb8f38f90c969bf5c5e.js
64 ms
app-b9f897cff7759cce3e90.js
116 ms
framework-1e12204b0a7f80a17b31.js
64 ms
webpack-runtime-9fdf1aa88a128dfd022b.js
55 ms
w.chatlio-widget.js
117 ms
j.php
138 ms
background.png
303 ms
DarkOqton.svg
300 ms
geomagic-controlx-light-56a1e78aefd4791cc9fb593d8a7969f2.svg
87 ms
en.png
301 ms
de.png
300 ms
fr.png
303 ms
it.png
301 ms
ja.png
512 ms
ko.png
513 ms
cn.png
535 ms
phone.svg
504 ms
us.png
404 ms
uk.png
510 ms
globe.svg
620 ms
key-visual-amphyon.webp
724 ms
media_1.png
744 ms
media_2.png
652 ms
resource.png
736 ms
OqtonLogo.svg
745 ms
ra-bootstrap.min.js
583 ms
w.chatlio-widget.js
23 ms
uc.js
101 ms
centrano2-bold-483b2dfbb6930d9becf272e5886c91c9.woff
566 ms
centrano2-extrabold-2149f4c0460d0821c08e8929ddbd8d86.woff
706 ms
centrano2-black-4e9227b157d86f9d9471542064effdca.woff
801 ms
centrano2-medium-3c5d88e60d773c0fd8e662e58e9861f7.woff
795 ms
centrano2-book-b8c8686691ad9d33e611770f99d0ef42.woff
678 ms
centrano2-thin-aab0b43a2ffa4081e4dd734e0c87049b.woff
940 ms
centrano2-hairline-c6b8b12c153cb9146a1e2487e2c201d8.woff
1009 ms
additive.works accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
additive.works best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
additive.works SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a valid hreflang
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Additive.works 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 Additive.works 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.
additive.works
Open Graph data is detected on the main page of Additive. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: