Tools & Wizards About Us
form-in.com screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    79% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 77% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

form-in.com

FORM.IN - FROM DESIGN TO FUNCTION Eschbach, made in Germany

Page Load Speed

1.4 sec in total

First Response

84 ms

Resources Loaded

1.2 sec

Page Rendered

105 ms

form-in.com screenshot

About Website

Visit form-in.com now to see the best up-to-date FORM IN content and also check out these interesting facts you probably never knew about form-in.com

FROM DESIGN TO FUNCTION Displays, Industrieprodukte, Präzisionsteile und Baugruppen Fertigung im Bereich Technik und Design, in Metall, Kunststoff und Holzwerkstoffen

Visit form-in.com

Key Findings

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

Performance Metrics

form-in.com performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

86/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value250 ms

84/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.3 s

39/100

10%

Network Requests Diagram

www.form-in.com

84 ms

originTrials.41d7301a.bundle.min.js

58 ms

minified.js

65 ms

focus-within-polyfill.js

61 ms

polyfill.min.js

428 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Form-in.com, 50% (18 requests) were made to Static.parastorage.com and 33% (12 requests) were made to Sentry-next.wixpress.com. The less responsive or slowest element that took the longest time to load (535 ms) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

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

Content Size

611.4 kB

After Optimization

327.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Form-in.com main page is 611.4 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 364.0 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 280.9 kB

  • Original 364.0 kB
  • After minification 362.4 kB
  • After compression 83.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. 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 280.9 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 18.5 kB
  • After minification 18.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. FORM IN images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.8 kB

  • Original 228.9 kB
  • After minification 228.8 kB
  • After compression 226.1 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. This website has mostly compressed JavaScripts.

Requests Breakdown

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

Requests Now

18

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of FORM IN. 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

www.form-in.com

www.form-in.com

84 ms

originTrials.41d7301a.bundle.min.js

originTrials.41d7301a.bundle.min.js

58 ms

minified.js

minified.js

65 ms

focus-within-polyfill.js

focus-within-polyfill.js

61 ms

polyfill.min.js

polyfill.min.js

428 ms

thunderbolt-commons.eb770ee8.bundle.min.js

thunderbolt-commons.eb770ee8.bundle.min.js

114 ms

main.578f27a3.bundle.min.js

main.578f27a3.bundle.min.js

114 ms

lodash.min.js

lodash.min.js

112 ms

react.production.min.js

react.production.min.js

113 ms

react-dom.production.min.js

react-dom.production.min.js

114 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

114 ms

wix-perf-measure.umd.min.js

wix-perf-measure.umd.min.js

115 ms

4e1a37_149fdd98eb0f443f9dd1cc082bcd7b18~mv2_d_1632_1224_s_2.jpg

4e1a37_149fdd98eb0f443f9dd1cc082bcd7b18~mv2_d_1632_1224_s_2.jpg

230 ms

form_in%20Logo%202017.png

form_in%20Logo%202017.png

535 ms

bundle.min.js

bundle.min.js

54 ms

Xyjz-jNkfiYuJf8UC3Lizw.woff

Xyjz-jNkfiYuJf8UC3Lizw.woff

54 ms

idLYXfFa1c7oAPILDl4z0fesZW2xOQ-xsNqO47m55DA.woff

idLYXfFa1c7oAPILDl4z0fesZW2xOQ-xsNqO47m55DA.woff

55 ms

121 ms

129 ms

138 ms

121 ms

120 ms

118 ms

153 ms

157 ms

158 ms

157 ms

156 ms

159 ms

deprecation-de.v5.html

deprecation-de.v5.html

6 ms

bolt-performance

bolt-performance

26 ms

deprecation-style.v5.css

deprecation-style.v5.css

8 ms

right-arrow.svg

right-arrow.svg

20 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

6 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

6 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

7 ms

Accessibility Review

form-in.com accessibility score

91

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

Best Practices

form-in.com 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

form-in.com 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

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Form-in.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Form-in.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

form-in.com

Open Graph data is detected on the main page of FORM IN. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: