Tools & Wizards About Us
ptw.de screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

ptw.de

Home | PTW

Page Load Speed

3.8 sec in total

First Response

368 ms

Resources Loaded

3.3 sec

Page Rendered

128 ms

ptw.de screenshot

About Website

Visit ptw.de now to see the best up-to-date PTW content for United States and also check out these interesting facts you probably never knew about ptw.de

PTW is a global market leader for dosimetry solutions in radiation therapy, diagnostic imaging, metrology and radiation monitoring.

Visit ptw.de

Key Findings

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

Performance Metrics

ptw.de performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value6.6 s

8/100

25%

SI (Speed Index)

Value6.9 s

34/100

10%

TBT (Total Blocking Time)

Value320 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0.936

3/100

15%

TTI (Time to Interactive)

Value6.6 s

58/100

10%

Network Requests Diagram

ptw.de

368 ms

home_start.html

759 ms

jquery-ui-1.9.2.custom.css

487 ms

stylesheet_904f59f47e.css

413 ms

flexslider.css

320 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 85% of them (44 requests) were addressed to the original Ptw.de, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (925 ms) belongs to the original domain Ptw.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 765.5 kB (50%)

Content Size

1.5 MB

After Optimization

755.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ptw.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. 35% of websites need less resources to load. Javascripts take 642.8 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 15.0 kB

  • Original 20.9 kB
  • After minification 19.4 kB
  • After compression 5.9 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 15.0 kB or 72% of the original size.

Image Optimization

-4%

Potential reduce by 19.4 kB

  • Original 494.6 kB
  • After minification 475.2 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. PTW images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 429.9 kB

  • Original 642.8 kB
  • After minification 599.4 kB
  • After compression 212.9 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 429.9 kB or 67% of the original size.

CSS Optimization

-83%

Potential reduce by 301.1 kB

  • Original 363.0 kB
  • After minification 337.3 kB
  • After compression 61.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. Ptw.de needs all CSS files to be minified and compressed as it can save up to 301.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (70%)

Requests Now

50

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ptw.de

ptw.de

368 ms

home_start.html

home_start.html

759 ms

jquery-ui-1.9.2.custom.css

jquery-ui-1.9.2.custom.css

487 ms

stylesheet_904f59f47e.css

stylesheet_904f59f47e.css

413 ms

flexslider.css

flexslider.css

320 ms

stylesheet_ffe2fc3d47.css

stylesheet_ffe2fc3d47.css

218 ms

jquery-1.5.1-1.8.11-1.2.5.js

jquery-1.5.1-1.8.11-1.2.5.js

837 ms

javascript_757c080409.js

javascript_757c080409.js

325 ms

ptw.css

ptw.css

416 ms

ptw_home.css

ptw_home.css

732 ms

slightbox.css

slightbox.css

537 ms

prototype.1.7.0.yui.js

prototype.1.7.0.yui.js

925 ms

scriptaculous.js

scriptaculous.js

521 ms

lightbox.2.0.5.yui.js

lightbox.2.0.5.yui.js

484 ms

xajax.js

xajax.js

631 ms

swfobject.js

swfobject.js

860 ms

flashmap.css

flashmap.css

582 ms

urchin.js

urchin.js

6 ms

jquery.min.js

jquery.min.js

32 ms

jquery.flexslider.js

jquery.flexslider.js

668 ms

jquery.flexslider.textmode.js

jquery.flexslider.textmode.js

564 ms

reset.css

reset.css

114 ms

t3-41.css

t3-41.css

115 ms

ptw_main.css

ptw_main.css

119 ms

ptw_menu.css

ptw_menu.css

163 ms

ptw_styles.css

ptw_styles.css

201 ms

ptw_plugins.css

ptw_plugins.css

205 ms

effects.js

effects.js

214 ms

builder.js

builder.js

109 ms

bgMain.png

bgMain.png

112 ms

PTW-logo.png

PTW-logo.png

109 ms

bgHeaderHome.png

bgHeaderHome.png

108 ms

c70871013d.png

c70871013d.png

528 ms

54693a293e.png

54693a293e.png

560 ms

4c85dcae88.png

4c85dcae88.png

533 ms

navMainNoL1.png

navMainNoL1.png

249 ms

searchButton.png

searchButton.png

252 ms

bgBoxHeader.png

bgBoxHeader.png

253 ms

42e2cb6aa2.png

42e2cb6aa2.png

323 ms

82d681072c.png

82d681072c.png

325 ms

41574d7233.png

41574d7233.png

323 ms

c88eb9ee38.png

c88eb9ee38.png

402 ms

b361e85be1.png

b361e85be1.png

434 ms

26709d1a43.png

26709d1a43.png

430 ms

__utm.gif

__utm.gif

38 ms

bgBoxHeaderReverse.png

bgBoxHeaderReverse.png

445 ms

DdcBg6TnRAE

DdcBg6TnRAE

108 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

22 ms

www-embed-player.js

www-embed-player.js

43 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

30 ms

ad_status.js

ad_status.js

25 ms

bg_direction_nav.png

bg_direction_nav.png

108 ms

Accessibility Review

ptw.de accessibility score

84

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

ptw.de best practices score

83

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

Page has valid source maps

SEO Factors

ptw.de SEO score

84

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

    DE

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ptw.de 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 Ptw.de main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

ptw.de

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