Tools & Wizards About Us
prs.de screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 94

    SEO

    Google-friendlier than
    90% of websites

prs.de

PRS GmbH | Tools for Command, Control and Information Systems

Page Load Speed

3 sec in total

First Response

370 ms

Resources Loaded

2.3 sec

Page Rendered

243 ms

prs.de screenshot

About Website

Visit prs.de now to see the best up-to-date PRS content and also check out these interesting facts you probably never knew about prs.de

PRS is one of the leading suppliers of dynamic, man-machine interfaces for applications that help to control and monitor processes in a variety of industrial segments.

Visit prs.de

Key Findings

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

Performance Metrics

prs.de performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.135

80/100

15%

TTI (Time to Interactive)

Value5.2 s

74/100

10%

Network Requests Diagram

prs.de

370 ms

www.prs.de

613 ms

myfonts.css

89 ms

system.base.css

175 ms

system.menus.css

262 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 96% of them (49 requests) were addressed to the original Prs.de, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (778 ms) belongs to the original domain Prs.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 428.2 kB (28%)

Content Size

1.5 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Prs.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. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 26.4 kB

  • Original 34.0 kB
  • After minification 32.6 kB
  • After compression 7.6 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 26.4 kB or 78% of the original size.

Image Optimization

-7%

Potential reduce by 76.4 kB

  • Original 1.1 MB
  • After minification 989.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. PRS images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 256.1 kB

  • Original 345.8 kB
  • After minification 248.7 kB
  • After compression 89.8 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 256.1 kB or 74% of the original size.

CSS Optimization

-82%

Potential reduce by 69.3 kB

  • Original 84.8 kB
  • After minification 62.5 kB
  • After compression 15.5 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. Prs.de needs all CSS files to be minified and compressed as it can save up to 69.3 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 38 (78%)

Requests Now

49

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

prs.de

prs.de

370 ms

www.prs.de

www.prs.de

613 ms

myfonts.css

myfonts.css

89 ms

system.base.css

system.base.css

175 ms

system.menus.css

system.menus.css

262 ms

system.messages.css

system.messages.css

264 ms

system.theme.css

system.theme.css

264 ms

views_slideshow.css

views_slideshow.css

265 ms

date.css

date.css

266 ms

datepicker.1.7.css

datepicker.1.7.css

264 ms

field.css

field.css

346 ms

node.css

node.css

348 ms

search.css

search.css

349 ms

user.css

user.css

349 ms

views.css

views.css

351 ms

ctools.css

ctools.css

350 ms

lightbox.css

lightbox.css

432 ms

views_slideshow_cycle.css

views_slideshow_cycle.css

434 ms

meanmenu.min.css

meanmenu.min.css

435 ms

superfish.css

superfish.css

434 ms

blue.css

blue.css

437 ms

base.css

base.css

436 ms

mx_style.css

mx_style.css

605 ms

jquery.min.js

jquery.min.js

693 ms

jquery-extend-3.4.0.js

jquery-extend-3.4.0.js

519 ms

jquery-html-prefilter-3.5.0-backport.js

jquery-html-prefilter-3.5.0-backport.js

520 ms

jquery.once.js

jquery.once.js

523 ms

drupal.js

drupal.js

523 ms

views_slideshow.js

views_slideshow.js

701 ms

lightbox.js

lightbox.js

702 ms

jquery.cycle.all.js

jquery.cycle.all.js

704 ms

views_slideshow_cycle.js

views_slideshow_cycle.js

611 ms

captcha.js

captcha.js

690 ms

jquery.meanmenu.min.js

jquery.meanmenu.min.js

706 ms

responsive_menus_mean_menu.js

responsive_menus_mean_menu.js

776 ms

googleanalytics.js

googleanalytics.js

778 ms

jquery.hoverIntent.minified.js

jquery.hoverIntent.minified.js

777 ms

sfsmallscreen.js

sfsmallscreen.js

778 ms

superfish.js

superfish.js

707 ms

supersubs.js

supersubs.js

618 ms

superfish.js

superfish.js

608 ms

analytics.js

analytics.js

24 ms

collect

collect

14 ms

keepthingsundercontrol.png

keepthingsundercontrol.png

91 ms

prs.png

prs.png

87 ms

containerbg.png

containerbg.png

89 ms

prs_startseite.jpg

prs_startseite.jpg

347 ms

prs_gipsy_frontpage_0.jpg

prs_gipsy_frontpage_0.jpg

435 ms

AX001402_72dpi.jpg

AX001402_72dpi.jpg

434 ms

download.png

download.png

175 ms

prs_watermark.png

prs_watermark.png

176 ms

Accessibility Review

prs.de accessibility score

84

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Links do not have a discernible name

Best Practices

prs.de best practices score

58

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

prs.de SEO score

94

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prs.de can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Prs.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

prs.de

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