Tools & Wizards About Us
additive.works screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

additive.works

Additive Manufacturing Simulation Software | Oqton

Page Load Speed

1.8 sec in total

First Response

102 ms

Resources Loaded

1.4 sec

Page Rendered

262 ms

additive.works screenshot

About Website

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

Key Findings

We analyzed Additive.works page load time and found that the first response time was 102 ms and then it took 1.7 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

additive.works performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

35/100

10%

LCP (Largest Contentful Paint)

Value71.4 s

0/100

25%

SI (Speed Index)

Value15.0 s

1/100

10%

TBT (Total Blocking Time)

Value2,050 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value75.3 s

0/100

10%

Network Requests Diagram

additive.works

102 ms

172 ms

gtm.js

103 ms

chatlio.js

6 ms

v4.js

94 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Additive.works, 81% (25 requests) were made to Oqton.com and 6% (2 requests) were made to W.chatlio.com. The less responsive or slowest element that took the longest time to load (862 ms) relates to the external source Oqton.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 10.0 MB (78%)

Content Size

12.9 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Additive.works main page is 12.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. 40% of websites need less resources to load. Javascripts take 11.8 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 265.2 kB

  • Original 349.9 kB
  • After minification 349.7 kB
  • After compression 84.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. 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 265.2 kB or 76% of the original size.

Image Optimization

-21%

Potential reduce by 153.6 kB

  • Original 737.8 kB
  • After minification 584.3 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 153.6 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-81%

Potential reduce by 9.6 MB

  • Original 11.8 MB
  • After minification 11.8 MB
  • After compression 2.2 MB

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 9.6 MB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (52%)

Requests Now

21

After Optimization

10

  • Images
  • JavaScript

The browser has sent 21 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 12 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

additive.works

additive.works

102 ms

172 ms

gtm.js

gtm.js

103 ms

chatlio.js

chatlio.js

6 ms

v4.js

v4.js

94 ms

webpack-runtime-4f374ce0c532cb52dd78.js

webpack-runtime-4f374ce0c532cb52dd78.js

26 ms

framework-436f9f5b2c17768fa162.js

framework-436f9f5b2c17768fa162.js

42 ms

75fc9c18-19928659922ba0de1367.js

75fc9c18-19928659922ba0de1367.js

38 ms

94726e6d-aeb8adf4530633a3ca34.js

94726e6d-aeb8adf4530633a3ca34.js

38 ms

f0cb6341-efe883c941321ae166c7.js

f0cb6341-efe883c941321ae166c7.js

48 ms

app-f7b4d577f70dfb299054.js

app-f7b4d577f70dfb299054.js

160 ms

w.chatlio-widget.js

w.chatlio-widget.js

60 ms

j.php

j.php

67 ms

background.png

background.png

305 ms

DarkOqton.svg

DarkOqton.svg

306 ms

geomagic-controlx-light-56a1e78aefd4791cc9fb593d8a7969f2.svg

geomagic-controlx-light-56a1e78aefd4791cc9fb593d8a7969f2.svg

34 ms

en.png

en.png

308 ms

phone.svg

phone.svg

307 ms

key-visual-amphyon.webp

key-visual-amphyon.webp

501 ms

media_1.png

media_1.png

327 ms

media_2.png

media_2.png

862 ms

resource.png

resource.png

447 ms

OqtonLogo.svg

OqtonLogo.svg

445 ms

w.chatlio-widget.js

w.chatlio-widget.js

20 ms

centrano2-bold-483b2dfbb6930d9becf272e5886c91c9.woff

centrano2-bold-483b2dfbb6930d9becf272e5886c91c9.woff

343 ms

centrano2-extrabold-2149f4c0460d0821c08e8929ddbd8d86.woff

centrano2-extrabold-2149f4c0460d0821c08e8929ddbd8d86.woff

340 ms

centrano2-black-4e9227b157d86f9d9471542064effdca.woff

centrano2-black-4e9227b157d86f9d9471542064effdca.woff

468 ms

centrano2-medium-3c5d88e60d773c0fd8e662e58e9861f7.woff

centrano2-medium-3c5d88e60d773c0fd8e662e58e9861f7.woff

560 ms

centrano2-book-b8c8686691ad9d33e611770f99d0ef42.woff

centrano2-book-b8c8686691ad9d33e611770f99d0ef42.woff

643 ms

centrano2-thin-aab0b43a2ffa4081e4dd734e0c87049b.woff

centrano2-thin-aab0b43a2ffa4081e4dd734e0c87049b.woff

762 ms

centrano2-hairline-c6b8b12c153cb9146a1e2487e2c201d8.woff

centrano2-hairline-c6b8b12c153cb9146a1e2487e2c201d8.woff

779 ms

Accessibility Review

additive.works accessibility score

95

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

additive.works 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

additive.works SEO score

80

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

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

Social Sharing Optimization

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: