2.7 sec in total
182 ms
2.4 sec
61 ms
Welcome to primerose.at homepage info - get ready to check Primerose best content right away, or after learning these important things about primerose.at
PrimeRose Public Relations ist Ihr kompetenter Sparringpartner in allen kommunikativen Angelegenheiten. Schwerpunkte: Health Care & Pharma Kommunikation, PR für Ärzte und Ordinationsgemeinschaften, Pu...
Visit primerose.atWe analyzed Primerose.at page load time and found that the first response time was 182 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
primerose.at performance score
name
value
score
weighting
Value3.0 s
51/100
10%
Value9.4 s
1/100
25%
Value7.3 s
29/100
10%
Value1,510 ms
14/100
30%
Value0.301
39/100
15%
Value18.5 s
3/100
10%
182 ms
30 ms
30 ms
79 ms
210 ms
Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Primerose.at, 46% (31 requests) were made to Static.wixstatic.com and 31% (21 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Static.wixstatic.com.
Page size can be reduced by 537.6 kB (49%)
1.1 MB
559.2 kB
In fact, the total size of Primerose.at main page is 1.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. HTML takes 668.0 kB which makes up the majority of the site volume.
Potential reduce by 532.0 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 532.0 kB or 80% of the original size.
Potential reduce by 1.3 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. Primerose images are well optimized though.
Potential reduce by 4.2 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.
Number of requests can be reduced by 10 (22%)
46
36
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Primerose. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and as a result speed up the page load time.
www.primerose.at
182 ms
minified.js
30 ms
focus-within-polyfill.js
30 ms
polyfill.min.js
79 ms
thunderbolt-commons.7700cd07.bundle.min.js
210 ms
main.16c08821.bundle.min.js
212 ms
main.renderer.1d21f023.bundle.min.js
210 ms
lodash.min.js
210 ms
react.production.min.js
212 ms
react-dom.production.min.js
233 ms
siteTags.bundle.min.js
232 ms
3bf9a8_01a5e7f7786a4a2084c75bb1827c0b36~mv2_d_3500_1338_s_2.jpg
358 ms
bundle.min.js
179 ms
3bf9a8_cac0221c93e241328d95fa6339335238~mv2_d_3011_3011_s_4_2.jpg
464 ms
3bf9a8_46842abcbb1b409fb11520690ec661cd~mv2.jpg
431 ms
3bf9a8_5f2eb21c66674b51b9e1b6b833ea1af2~mv2.jpg
500 ms
3bf9a8_adcbad3441744704bb5a971894699ec0~mv2.jpg
463 ms
3bf9a8_c517c06c596c4106946706b14e26d87b~mv2_d_5174_3544_s_4_2.jpg
567 ms
3bf9a8_b72efb65b35e4ef4bbd94f98922964bb~mv2.jpg
386 ms
3bf9a8_9952fbecbbf74c5da3e8c33d7ce4fe3a~mv2.jpg
529 ms
3bf9a8_92ebfc8331774bc59513ac0338e39607~mv2.jpg
639 ms
3bf9a8_9ae326c353e54d60ad147842987665c5~mv2.jpg
687 ms
3bf9a8_9ac4362e1ff741828842a968ebc46d2c~mv2.jpg
665 ms
3bf9a8_74c1beaad1174f1e8a68de828b2b5aa9~mv2.jpg
770 ms
3bf9a8_1ebe182ed44f4ad4b24f5953bb34e973~mv2.jpg
716 ms
3bf9a8_e31be464d7cb4486b89b2c58de77a33e~mv2.jpg
756 ms
3bf9a8_452accf9cf58449db808d58eae2deb4b~mv2.jpg
836 ms
3bf9a8_1545cbb17078424e8ec91f72c8c67e1d~mv2.jpg
813 ms
3bf9a8_955b56ef2ee443b3997eb1add5a56e34~mv2.jpg
851 ms
3bf9a8_acec779535eb4d05b132092cbdcba086~mv2.jpg
923 ms
3bf9a8_145f608600284ef791dab68cd38e2080~mv2.jpg
962 ms
3bf9a8_03791f6a2d894b6f9df1574a1da31b8f~mv2.jpg
975 ms
3bf9a8_1735df10c6cf466096b2995444c3ab4e~mv2.jpg
1024 ms
3bf9a8_5a85cfb2baf8451c9b9038ccc490db53~mv2.jpg
1050 ms
3bf9a8_a1593886037c458689f118ebb5895837~mv2.jpg
1056 ms
3bf9a8_ba3846daa3654e63830edb816bd03f67~mv2.jpg
1160 ms
3bf9a8_1e570d8f20c84450a84b368cfb9e3a2c~mv2.jpg
1184 ms
3bf9a8_bb46a7a67d5d42c993242c752d9d9a87~mv2.jpg
1149 ms
3bf9a8_52a02d0bdcb94c8c8f39c0d1e5312fc8~mv2.jpg
1271 ms
3bf9a8_294848d2894e4cc9ae45432b8dbe4a75~mv2.jpg
1203 ms
3bf9a8_957ae29e9257408890decb6eb65bbcc8~mv2.jpg
1254 ms
8d13be_bcb2da648cc344db8e43c45986dbaa4a.png
1257 ms
8d13be_f158bd26d848468b9838f1b4c5738b2b.png
1276 ms
4d1b9848-7ebd-472c-9d31-4af0aa7faaea.woff
45 ms
e04da7b7-ccbf-4cbf-b19a-947551d17de6.woff
45 ms
908c4810-64db-4b46-bb8e-823eb41f68c0.woff
44 ms
opensans-bold-webfont.woff
47 ms
opensans-regular-webfont.woff
47 ms
4021a3b9-f782-438b-aeb4-c008109a8b64.woff
45 ms
b56b944e-bbe0-4450-a241-de2125d3e682.woff
45 ms
6f8d1983-4d34-4fa4-9110-988f6c495757.woff
46 ms
61bd362e-7162-46bd-b67e-28f366c4afbe.woff
46 ms
121 ms
110 ms
114 ms
115 ms
114 ms
113 ms
158 ms
158 ms
154 ms
148 ms
151 ms
147 ms
deprecation-de.v5.html
7 ms
bolt-performance
37 ms
deprecation-style.v5.css
13 ms
right-arrow.svg
11 ms
primerose.at accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
button, link, and menuitem elements do not have accessible names.
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
primerose.at 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
primerose.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
Tap targets are not sized appropriately
![]()
EN
![]()
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Primerose.at 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 Primerose.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.
primerose.at
Open Graph data is detected on the main page of Primerose. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: