2.6 sec in total
48 ms
2 sec
536 ms
Click here to check amazing Queisser content. Otherwise, check out these important facts you probably never knew about queisser.com
Explore the world of Queisser Pharma, with quality products of pharmaceuticals, medical devices, food supplements and cosmetics. Here's more!
Visit queisser.comWe analyzed Queisser.com page load time and found that the first response time was 48 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.
queisser.com performance score
name
value
score
weighting
Value2.2 s
79/100
10%
Value6.1 s
12/100
25%
Value2.2 s
99/100
10%
Value180 ms
92/100
30%
Value0
100/100
15%
Value4.8 s
79/100
10%
48 ms
60 ms
18 ms
32 ms
40 ms
Our browser made a total of 60 requests to load all elements on the main page. We found that all of those requests were addressed to Queisser.com and no external sources were called. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Queisser.com.
Page size can be reduced by 143.2 kB (9%)
1.6 MB
1.4 MB
In fact, the total size of Queisser.com main page is 1.6 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. 45% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 140.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 140.0 kB or 85% of the original size.
Potential reduce by 3.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. Queisser images are well optimized though.
Number of requests can be reduced by 39 (67%)
58
19
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Queisser. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
queisser.com
48 ms
www.queisser.com
60 ms
eac8cf8.css
18 ms
ffce95a.css
32 ms
c1d6422.css
40 ms
11c2f39.css
51 ms
1f5a5e6.css
52 ms
bc0f8e7.css
53 ms
856b846.css
31 ms
cebeb0f.css
50 ms
f394750.css
53 ms
3b6ec37.css
69 ms
bdda3eb.css
65 ms
051336f.css
62 ms
68cda21.css
63 ms
f423d87.css
66 ms
5c0dd2e.js
99 ms
61e3009.js
98 ms
14a4bdb.js
95 ms
b5f5d83.js
97 ms
b35efea.js
94 ms
4a479ff.js
100 ms
aefd60a.js
102 ms
49a0fac.js
101 ms
4e4ba5c.js
102 ms
8d952f6.js
103 ms
01a5ac5.js
105 ms
104f8e9.js
108 ms
b0772f9.js
103 ms
191381d.js
106 ms
f879c81.js
105 ms
42f63d7.js
114 ms
fa42083.js
120 ms
59c7ec9.js
130 ms
30e390a.js
122 ms
6eb8b05.js
123 ms
22c27d9.js
129 ms
43d934c.js
126 ms
066185a.js
134 ms
5cf61d4.js
119 ms
5842dcf.js
122 ms
c5947ac.js
113 ms
60d900d.js
117 ms
csm_startseite_meetingsituation_queisser_c544729470.jpg
819 ms
logo-doppelherz.svg
111 ms
logo-protefix.svg
112 ms
csm_logo-stozzon_f41b57bc24.png
547 ms
logo-ramend.svg
114 ms
csm_logo-tigerbalm_a9d64d0cb1.png
576 ms
csm_logo-litozin_1c82de2cce.png
438 ms
csm_international_produktrange_queisser_f6e1ac204d.jpg
833 ms
csm_queisser-leitbild-teaser-604x400_ca2329842f.jpg
700 ms
csm_teaser_karriere_queisser_84f2131ce3.jpg
949 ms
csm_teaser_nachhaltigkeit_massnahmen_queisser_7143c00945.jpg
1086 ms
csm_teaser_neue-firmenzentrale_queisser_2f4ccc9f38.jpg
1176 ms
csm_teaser_soziales_engagement_queisser_5f795ca3a2.jpg
1236 ms
csm_karriere_startseite_queisser_dc86f47aa3.jpg
1296 ms
csm_top-job-2022_68674cf86f.jpg
1326 ms
csm_total_e-quality_guetesiegel_6ec8b26c8f.jpg
1384 ms
csm_campus_mockup_queisser_05b4287332.jpg
1808 ms
queisser.com 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
Image elements do not have [alt] attributes
Links do not have a discernible name
queisser.com 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
queisser.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Queisser.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Queisser.com 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.
queisser.com
Open Graph description is not detected on the main page of Queisser. 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: