Tools & Wizards About Us

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

fx64.de

Autodesk Inventor Tools & Customizations by FX64 Software Solutions

Page Load Speed

3.3 sec in total

First Response

400 ms

Resources Loaded

2.8 sec

Page Rendered

63 ms

About Website

Click here to check amazing FX64 content. Otherwise, check out these important facts you probably never knew about fx64.de

We are extending Inventor capabilities for almost two decades! Need a custom solution? Let us know about it! Try our Autodesk certified solutions!

Visit fx64.de

Key Findings

We analyzed Fx64.de page load time and found that the first response time was 400 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

fx64.de performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

31/100

25%

SI (Speed Index)

Value6.2 s

44/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0.055

98/100

15%

TTI (Time to Interactive)

Value12.0 s

16/100

10%

Network Requests Diagram

fx64.de

400 ms

fx64.de

440 ms

www.fx64online.com

1445 ms

minified.js

42 ms

focus-within-polyfill.js

35 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 6% of them (2 requests) were addressed to the original Fx64.de, 41% (14 requests) were made to Static.parastorage.com and 35% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Fx64online.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 289.9 kB (46%)

Content Size

630.1 kB

After Optimization

340.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Fx64.de main page is 630.1 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. 35% of websites need less resources to load. HTML takes 322.1 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 241.7 kB

  • Original 322.1 kB
  • After minification 320.3 kB
  • After compression 80.3 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 241.7 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 4.5 kB
  • After minification 4.5 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. FX64 images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 48.1 kB

  • Original 303.5 kB
  • After minification 303.5 kB
  • After compression 255.4 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 48.1 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (59%)

Requests Now

17

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

fx64.de accessibility score

86

Accessibility Issues

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Links do not have a discernible name

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

fx64.de best practices score

92

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

Page has valid source maps

SEO Factors

fx64.de 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 Fx64.de 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 Fx64.de 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

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: