5 sec in total
217 ms
3.1 sec
1.7 sec
Visit openpr.de now to see the best up-to-date OpenPR content for Germany and also check out these interesting facts you probably never knew about openpr.de
PR Portal online + Deutschland ▶️ Jetzt Online Pressemitteilungen kostenlos verbreiten mit dem Presseportal openPR ✅ 20 Jahre online PR.
Visit openpr.deWe analyzed Openpr.de page load time and found that the first response time was 217 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
openpr.de performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value4.0 s
49/100
25%
Value7.1 s
31/100
10%
Value930 ms
30/100
30%
Value0
100/100
15%
Value8.4 s
38/100
10%
217 ms
393 ms
502 ms
186 ms
286 ms
Our browser made a total of 74 requests to load all elements on the main page. We found that 28% of them (21 requests) were addressed to the original Openpr.de, 55% (41 requests) were made to Cdn.open-pr.de and 7% (5 requests) were made to D.delivery.consentmanager.net. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Cdn.open-pr.de.
Page size can be reduced by 212.7 kB (14%)
1.5 MB
1.3 MB
In fact, the total size of Openpr.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. 55% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 177.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 177.9 kB or 80% of the original size.
Potential reduce by 32.4 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. OpenPR images are well optimized though.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Potential reduce by 200 B
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. Openpr.de has all CSS files already compressed.
Number of requests can be reduced by 14 (20%)
69
55
The browser has sent 69 CSS, Javascripts, AJAX and image requests in order to completely render the main page of OpenPR. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
openpr.de
217 ms
openpr.de
393 ms
www.openpr.de
502 ms
fonts.css
186 ms
openpr.css
286 ms
all.min.css
382 ms
jquery.min.js
402 ms
bootstrap.min.js
284 ms
jquery.sidr.min.js
284 ms
openpr.js
285 ms
cmp.php
452 ms
cmp_final.min.js
224 ms
matomo.js
520 ms
c05f7ea3.500x375.jpg
785 ms
openpr-logo-slogan.svg
111 ms
flagge-de.svg
111 ms
flagge-uk.svg
114 ms
openpr-fuer-fachleute.jpg
113 ms
openpr-logo-i.svg
107 ms
logo-google-news.svg
111 ms
openpr-logo.svg
204 ms
c55f7ea3.500x375.jpg
872 ms
655f7ea3.500x375.jpg
778 ms
555f7ea3.500x375.jpg
113 ms
cc4f7ea3.500x375.jpg
113 ms
584f7ea3.500x375.jpg
121 ms
255f7ea3.500x375.jpg
120 ms
c35f7ea3.500x375.jpg
917 ms
645f7ea3.500x375.jpg
122 ms
f35f7ea3.500x375.jpg
748 ms
a45f7ea3.500x375.jpg
748 ms
945f7ea3.500x375.jpg
747 ms
b45f7ea3.500x375.jpg
804 ms
845f7ea3.500x375.jpg
888 ms
245f7ea3.500x375.jpg
964 ms
145f7ea3.500x375.jpg
775 ms
455f7ea3.500x375.jpg
778 ms
355f7ea3.500x375.jpg
1010 ms
e35f7ea3.500x375.jpg
1176 ms
b15f7ea3.500x375.jpg
1058 ms
335f7ea3.500x375.jpg
891 ms
5f4f7ea3.500x375.jpg
1256 ms
694f7ea3.500x375.jpg
1110 ms
1f3f7ea3.500x375.jpg
1375 ms
e25f7ea3.500x375.jpg
1345 ms
725f7ea3.500x375.jpg
1241 ms
745f7ea3.500x375.jpg
1118 ms
635f7ea3.500x375.jpg
1341 ms
525f7ea3.500x375.jpg
1176 ms
305f7ea3.500x375.jpg
1178 ms
415f7ea3.500x375.jpg
1428 ms
a05f7ea3.500x375.jpg
1431 ms
e45f7ea3.500x375.jpg
1422 ms
915f7ea3.500x375.jpg
1354 ms
860f7ea3.500x375.jpg
1349 ms
825f7ea3.500x375.jpg
1515 ms
openpr-premium.json
121 ms
openpr-agenturverzeichnis.json
117 ms
fa-solid-900.ttf
409 ms
fa-regular-400.ttf
300 ms
055f7ea3.500x375.jpg
1430 ms
f45f7ea3.500x375.jpg
1271 ms
c55f7ea3.120x80.jpg
1180 ms
215f7ea3.120x80.jpg
1181 ms
415f7ea3.120x80.jpg
1457 ms
cmp.php
107 ms
matomo.php
253 ms
bV8xLndfMTUxMjcucl9DQ1BBLmxfZW4uZF82MDYwLnhfMTAudi5wLnRfNjA2MC54dF8xMA.js
13 ms
bV8xLndfMTUxMjcucl9DQ1BBLmxfZGUuZF82MDYwLnhfMTAucC52LnRfNjA2MC54dF8xMA.js
13 ms
101 ms
logo1595248860x7816.png
37 ms
cmplogo.svg
31 ms
138 ms
consent.php
240 ms
openpr.de accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Links do not have a discernible name
openpr.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
openpr.de SEO score
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
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Openpr.de 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 Openpr.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.
openpr.de
Open Graph data is detected on the main page of OpenPR. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: