Tools & Wizards About Us
pi.de screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    62% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 90

    SEO

    Google-friendlier than
    69% of websites

pi.de

Physik Instrumente (PI) – Lösungen für präzise Bewegung und Positionierung

Page Load Speed

2.8 sec in total

First Response

367 ms

Resources Loaded

2.1 sec

Page Rendered

270 ms

pi.de screenshot

About Website

Welcome to pi.de homepage info - get ready to check PI best content right away, or after learning these important things about pi.de

Weltbewegende Antriebslösungen von Physik Instrumente (PI) – Piezo-Positioniersysteme, Piezotechnik und Piezosysteme für die Nanopositionierung.

Visit pi.de

Key Findings

We analyzed Pi.de page load time and found that the first response time was 367 ms and then it took 2.4 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.

Performance Metrics

pi.de performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

43/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value1,140 ms

22/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value10.0 s

26/100

10%

Network Requests Diagram

www.physikinstrumente.de

367 ms

stylesheet_c068b5dd31.css

114 ms

javascript_04b8fee87d.js

188 ms

reset.css

202 ms

core.css

212 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Pi.de, 8% (4 requests) were made to S.ytimg.com and 6% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (988 ms) relates to the external source Physikinstrumente.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 555.5 kB (37%)

Content Size

1.5 MB

After Optimization

939.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pi.de main page is 1.5 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. 60% of websites need less resources to load. Images take 749.2 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 33.7 kB

  • Original 42.7 kB
  • After minification 33.1 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 9.6 kB, which is 23% 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 33.7 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 22.8 kB

  • Original 749.2 kB
  • After minification 726.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. PI images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 250.4 kB

  • Original 402.0 kB
  • After minification 389.7 kB
  • After compression 151.7 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 250.4 kB or 62% of the original size.

CSS Optimization

-83%

Potential reduce by 248.7 kB

  • Original 300.6 kB
  • After minification 289.5 kB
  • After compression 51.9 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. Pi.de needs all CSS files to be minified and compressed as it can save up to 248.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 31 (62%)

Requests Now

50

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.physikinstrumente.de

www.physikinstrumente.de

367 ms

stylesheet_c068b5dd31.css

stylesheet_c068b5dd31.css

114 ms

javascript_04b8fee87d.js

javascript_04b8fee87d.js

188 ms

reset.css

reset.css

202 ms

core.css

core.css

212 ms

navigation.css

navigation.css

215 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

311 ms

waypoints.min.js

waypoints.min.js

223 ms

jquery.dotdotdot-1.5.2-packed.js

jquery.dotdotdot-1.5.2-packed.js

283 ms

searchform.js

searchform.js

308 ms

jquery.cookie.js

jquery.cookie.js

328 ms

videoslider.css

videoslider.css

329 ms

slightbox.css

slightbox.css

332 ms

slimbox.2.0.4.yui.js

slimbox.2.0.4.yui.js

394 ms

default.js

default.js

419 ms

overview.js

overview.js

421 ms

gtm.js

gtm.js

49 ms

analytics.js

analytics.js

4 ms

collect

collect

96 ms

Physik-Instrumente-Logo.png

Physik-Instrumente-Logo.png

113 ms

PI_Bewegen_Positionieren.png

PI_Bewegen_Positionieren.png

113 ms

PI_Icon_Contact_01.png

PI_Icon_Contact_01.png

114 ms

global_04.png

global_04.png

103 ms

pi_icon_login.png

pi_icon_login.png

109 ms

nav-bar-bg.gif

nav-bar-bg.gif

110 ms

search-btn.png

search-btn.png

218 ms

shopping-cart.png

shopping-cart.png

222 ms

video_play.png

video_play.png

221 ms

pixel.gif

pixel.gif

305 ms

thumb_inactive.gif

thumb_inactive.gif

305 ms

6216ce9a0c.jpg

6216ce9a0c.jpg

306 ms

089b382713.jpg

089b382713.jpg

988 ms

d340d682ab.jpg

d340d682ab.jpg

333 ms

be72936f91.jpg

be72936f91.jpg

332 ms

Fair_FOM_Taiwan_2016_Overview.jpg

Fair_FOM_Taiwan_2016_Overview.jpg

333 ms

Overview_SPIE_Photonics_Europe.jpg

Overview_SPIE_Photonics_Europe.jpg

332 ms

Footer_PI_Logo.png

Footer_PI_Logo.png

339 ms

youtube_12.png

youtube_12.png

443 ms

twitter_08.png

twitter_08.png

441 ms

iframe_api

iframe_api

63 ms

thumb_active.gif

thumb_active.gif

361 ms

page-nav.png

page-nav.png

363 ms

page-nav-active.png

page-nav-active.png

372 ms

d3SweKJ0Lsg

d3SweKJ0Lsg

56 ms

www-widgetapi.js

www-widgetapi.js

9 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

25 ms

www-embed-player.js

www-embed-player.js

49 ms

base.js

base.js

76 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

49 ms

ad_status.js

ad_status.js

44 ms

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf

44 ms

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf

47 ms

collect

collect

3 ms

Accessibility Review

pi.de accessibility score

81

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

pi.de best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

pi.de SEO score

90

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

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

    DE

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

pi.de

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