10.5 sec in total
1.2 sec
8.9 sec
295 ms
Welcome to prinz.at homepage info - get ready to check PRINZ best content for Russia right away, or after learning these important things about prinz.at
Visit prinz.atWe analyzed Prinz.at page load time and found that the first response time was 1.2 sec and then it took 9.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
prinz.at performance score
name
value
score
weighting
Value10.3 s
0/100
10%
Value11.2 s
0/100
25%
Value23.9 s
0/100
10%
Value11,430 ms
0/100
30%
Value0.392
26/100
15%
Value36.4 s
0/100
10%
1245 ms
219 ms
658 ms
344 ms
30 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 75% of them (65 requests) were addressed to the original Prinz.at, 9% (8 requests) were made to Fonts.gstatic.com and 5% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.2 sec) relates to the external source Vidalifinishing.com.
Page size can be reduced by 1.2 MB (54%)
2.1 MB
972.8 kB
In fact, the total size of Prinz.at main page is 2.1 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. 50% of websites need less resources to load. Images take 827.3 kB which makes up the majority of the site volume.
Potential reduce by 40.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 40.1 kB or 78% of the original size.
Potential reduce by 136.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. Obviously, PRINZ needs image optimization as it can save up to 136.2 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 391.0 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 391.0 kB or 68% of the original size.
Potential reduce by 595.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. Prinz.at needs all CSS files to be minified and compressed as it can save up to 595.5 kB or 87% of the original size.
Number of requests can be reduced by 54 (71%)
76
22
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PRINZ. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 28 to 1 for CSS and as a result speed up the page load time.
www.prinz.at
1245 ms
wp-emoji-release.min.js
219 ms
cache.skin.css
658 ms
layerslider.css
344 ms
css
30 ms
styles.css
244 ms
css
37 ms
css
47 ms
css
47 ms
bootstrap.min.css
681 ms
animate.css
503 ms
jquery.mCustomScrollbar.css
324 ms
font-awesome.min.css
497 ms
colorbox.css
455 ms
settings.css
456 ms
h1.css
636 ms
flexslider.css
641 ms
rivathemes.css
640 ms
component.css
642 ms
style.css
1107 ms
layerslider.css
761 ms
color1.css
755 ms
responsive.css
756 ms
color.php
1305 ms
icomoon.css
901 ms
font-awesome.css
985 ms
js_composer.css
1109 ms
event-list.css
993 ms
jquery.js
1132 ms
jquery-migrate.min.js
1113 ms
layerslider.kreaturamedia.jquery.js
1340 ms
greensock.js
1210 ms
layerslider.transitions.js
1219 ms
modernizr-2.6.2-respond-1.1.0.min.js
1219 ms
twitterFetcher_v10_min.js
1245 ms
js
23 ms
jquery.rivathemes.js
1438 ms
nyroModal.css
1482 ms
jquery.form.min.js
1480 ms
scripts.js
1478 ms
bootstrap.min.js
1563 ms
jquery.mCustomScrollbar.min.js
1291 ms
jquery.mousewheel.min.js
1348 ms
jquery.colorbox-min.js
1273 ms
preloadCssImages.jQuery_v5.js
1321 ms
jquery.stellar.min.js
1204 ms
imagesloaded.pkgd.min.js
1208 ms
jquery.flexslider-min.js
1225 ms
jquery.fitvids.js
1223 ms
envor.js
1156 ms
menu_functions.js
1203 ms
jquery.nyroModal.custom.min.js
1269 ms
wpfixedverticalfeedbackbuttonfront.js
1200 ms
js_composer_front.js
1192 ms
PrinzLogo.png
318 ms
retrive_image.php
4241 ms
logo.png
380 ms
Tra_Teknik_logo.jpg
375 ms
drema_160x110.jpg
667 ms
am1.jpg
141 ms
Button.png
531 ms
gb.png
436 ms
blank.gif
529 ms
austimber20163.jpg
530 ms
bIcY3_3JNqUVRAQQRNVteQ.ttf
21 ms
CcKI4k9un7TZVWzRVT-T8y3USBnSvpkopQaUR-2r7iU.ttf
23 ms
-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf
24 ms
8KhZd3VQBtXTAznvKjw-ky3USBnSvpkopQaUR-2r7iU.ttf
21 ms
RJMlAoFXXQEzZoMSUteGWKCWcynf_cDxXwCLxiixG1c.ttf
21 ms
xkvoNo9fC8O2RDydKj12by3USBnSvpkopQaUR-2r7iU.ttf
23 ms
JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf
23 ms
1ImRNPx4870-D9a1EBUdPC3USBnSvpkopQaUR-2r7iU.ttf
23 ms
fontawesome-webfont.woff
529 ms
fontawesome-webfont.woff
552 ms
date-separator.png
534 ms
analytics.js
18 ms
jquery.mousewheel.min.js
21 ms
collect
12 ms
skin.css
296 ms
skin.png
145 ms
Europe3.jpg
742 ms
MC_mit_EL-e1457334893845.png
589 ms
SchieneEL-e1457350284871.png
454 ms
AR-STIHL-ES120-e1457339404715.png
211 ms
GR-TKS-3mm-e1457339432482.png
217 ms
Procut-e1457337934572.png
380 ms
loading.gif
183 ms
prinz.at accessibility score
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
prinz.at best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
prinz.at SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prinz.at can be misinterpreted by Google and other search engines. Our service has detected that German is used on the page, and it matches the claimed language. Our system also found out that Prinz.at 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.
prinz.at
Open Graph description is not detected on the main page of PRINZ. 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: