Tools & Wizards About Us
rofin-sinar.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

rofin-sinar.com

Leader in Laser Solutions and Photonics Technology | Coherent

Page Load Speed

6.9 sec in total

First Response

348 ms

Resources Loaded

6.3 sec

Page Rendered

255 ms

rofin-sinar.com screenshot

About Website

Click here to check amazing Rofin Sinar content for United States. Otherwise, check out these important facts you probably never knew about rofin-sinar.com

A leading supplier of lasers, optics, and sensors for more than 50 years

Visit rofin-sinar.com

Key Findings

We analyzed Rofin-sinar.com page load time and found that the first response time was 348 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

rofin-sinar.com performance score

0

Network Requests Diagram

rofin-sinar.com

348 ms

www.rofin.com

334 ms

www.rofin.com

1306 ms

stylesheet_e443601f41.css

324 ms

events.css

332 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Rofin-sinar.com, 87% (46 requests) were made to Rofin.com and 4% (2 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Rofin.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 445.4 kB (38%)

Content Size

1.2 MB

After Optimization

714.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rofin-sinar.com main page is 1.2 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. 30% of websites need less resources to load. Images take 660.2 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 61.2 kB

  • Original 73.5 kB
  • After minification 64.5 kB
  • After compression 12.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. This page needs HTML code to be minified as it can gain 9.0 kB, which is 12% 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 61.2 kB or 83% of the original size.

Image Optimization

-4%

Potential reduce by 26.2 kB

  • Original 660.2 kB
  • After minification 634.0 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. Rofin Sinar images are well optimized though.

JavaScript Optimization

-84%

Potential reduce by 243.7 kB

  • Original 291.0 kB
  • After minification 162.7 kB
  • After compression 47.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 243.7 kB or 84% of the original size.

CSS Optimization

-85%

Potential reduce by 114.4 kB

  • Original 135.0 kB
  • After minification 101.9 kB
  • After compression 20.6 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. Rofin-sinar.com needs all CSS files to be minified and compressed as it can save up to 114.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (63%)

Requests Now

48

After Optimization

18

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rofin-sinar.com

rofin-sinar.com

348 ms

www.rofin.com

www.rofin.com

334 ms

www.rofin.com

www.rofin.com

1306 ms

stylesheet_e443601f41.css

stylesheet_e443601f41.css

324 ms

events.css

events.css

332 ms

form.css

form.css

330 ms

diu_contentelements.css

diu_contentelements.css

339 ms

selectboxes.css

selectboxes.css

338 ms

glossar.css

glossar.css

339 ms

jquery-1.9.1.js

jquery-1.9.1.js

1210 ms

jquery-ui.min.js

jquery-ui.min.js

41 ms

javascript_9a38f34785.js

javascript_9a38f34785.js

657 ms

rofin_style.css

rofin_style.css

771 ms

functions.js

functions.js

670 ms

slightbox.css

slightbox.css

668 ms

slimbox.2.0.4.yui.js

slimbox.2.0.4.yui.js

672 ms

jquery-ui.css

jquery-ui.css

55 ms

events.js

events.js

981 ms

ajax.js

ajax.js

1008 ms

ajax.js

ajax.js

1004 ms

hintergrund_verlauf.png

hintergrund_verlauf.png

113 ms

t.js

t.js

773 ms

menu1_produkte.png

menu1_produkte.png

748 ms

Applications_197x513.png

Applications_197x513.png

858 ms

menu3_maerkte_01.png

menu3_maerkte_01.png

804 ms

menu_service.png

menu_service.png

694 ms

menu_company_197x220.png

menu_company_197x220.png

799 ms

IR_Navibild_197x427.png

IR_Navibild_197x427.png

694 ms

menu_presse_197x205.png

menu_presse_197x205.png

1448 ms

menu_infocenter_197x135.png

menu_infocenter_197x135.png

1359 ms

transparent_print.png

transparent_print.png

1077 ms

home-button.png

home-button.png

1133 ms

transparent_social_youtube.png

transparent_social_youtube.png

1136 ms

transparent_social_twitter.png

transparent_social_twitter.png

1179 ms

transparent_social_facebook.png

transparent_social_facebook.png

1409 ms

transparent_white-newsletter.png

transparent_white-newsletter.png

1460 ms

transparent_white-arrow_rechts.png

transparent_white-arrow_rechts.png

1469 ms

transparent_contact.png

transparent_contact.png

1507 ms

transparent_weltweit_ot.png

transparent_weltweit_ot.png

1786 ms

TUBE_Landing_Page_Banner_262px_EN.jpg

TUBE_Landing_Page_Banner_262px_EN.jpg

1847 ms

header_neu_01.jpg

header_neu_01.jpg

2344 ms

header_neu_02.jpg

header_neu_02.jpg

2215 ms

header_neu_03.jpg

header_neu_03.jpg

2224 ms

furtherpress.png

furtherpress.png

1826 ms

cnt_js.php

cnt_js.php

396 ms

cnt_js.php

cnt_js.php

403 ms

shadow_verlauf.png

shadow_verlauf.png

1448 ms

head_keinbild.jpg

head_keinbild.jpg

1479 ms

flagge_de.png

flagge_de.png

1502 ms

suche_submit.png

suche_submit.png

1767 ms

Arial-Light.otf

Arial-Light.otf

2232 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

3 ms

futul___-webfont.woff

futul___-webfont.woff

2003 ms

SEO Factors

rofin-sinar.com SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Rofin-sinar.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is German. Our system also found out that Rofin-sinar.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

rofin-sinar.com

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