5.1 sec in total
135 ms
4.6 sec
426 ms
Visit cayston.com now to see the best up-to-date CAYSTON content and also check out these interesting facts you probably never knew about cayston.com
Official patient website for CAYSTON (aztreonam for inhalation solution). Learn about study results, treatment, dosing, side effects and financial assistance.
Visit cayston.comWe analyzed Cayston.com page load time and found that the first response time was 135 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
cayston.com performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value5.8 s
15/100
25%
Value22.9 s
0/100
10%
Value11,350 ms
0/100
30%
Value0.114
86/100
15%
Value36.3 s
0/100
10%
135 ms
181 ms
354 ms
45 ms
575 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 8% of them (5 requests) were addressed to the original Cayston.com, 52% (33 requests) were made to Cayston-cdn-1.s3-us-west-1.amazonaws.com and 13% (8 requests) were made to . The less responsive or slowest element that took the longest time to load (3.1 sec) relates to the external source Cayston-cdn-1.s3-us-west-1.amazonaws.com.
Page size can be reduced by 6.7 MB (9%)
75.5 MB
68.7 MB
In fact, the total size of Cayston.com main page is 75.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. Only a small number of websites need less resources to load. Images take 74.5 MB which makes up the majority of the site volume.
Potential reduce by 153.8 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 153.8 kB or 83% of the original size.
Potential reduce by 6.5 MB
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. CAYSTON images are well optimized though.
Potential reduce by 93 B
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 46.3 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. Cayston.com needs all CSS files to be minified and compressed as it can save up to 46.3 kB or 19% of the original size.
Number of requests can be reduced by 8 (15%)
53
45
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CAYSTON. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.
www.cayston.com
135 ms
gtm.js
181 ms
fonts.css
354 ms
patient-application-6b25f35bf918e7380c7c4a2b4dad2b25b54fbb71a3bb73d03ca1819ed90c88bf.css
45 ms
cayston-email-icon.svg
575 ms
Twitter.svg
576 ms
Facebook.svg
579 ms
email-decode.min.js
121 ms
application-257d65b529f5a431f3c5e156f718731ff9e13aa5812c4b1383337e301324c337.js
293 ms
svg-symbols-360a96e201.svg
204 ms
cayston-share.svg
551 ms
patient-logo.svg
752 ms
js
66 ms
12CF38EC47D4CF067.css
526 ms
MobileHeaderImage.jpeg
140 ms
scroll_down_arrow.png
136 ms
gilead-logo-new.svg
125 ms
GILCAY516425_CaystonPatientBrochure_2-0page1-refresh.jpg
1488 ms
GILCAY516425_Interactive_CaystonPatientBrochure_5-1_PatientBrochurePRCUpdate_2.jpg
1465 ms
GILCAY516425_CaystonPatientBrochure_2-0page3-refresh.jpg
1445 ms
GILCAY516425_CaystonPatientBrochure_2-0page4-refresh.jpg
1567 ms
GILCAY516425_CaystonPatientBrochure_2-0page5-refresh.jpg
1844 ms
GILCAY516425_Interactive_CaystonPatientBrochure_5-1_PatientBrochurePRCUpdate_6.jpg
1424 ms
GILCAY516425_CaystonPatientBrochure_2-0page7-refresh.jpg
1491 ms
GILCAY516425_Interactive_CaystonPatientBrochure_5-1_PatientBrochurePRCUpdate_8.jpg
1875 ms
page9-popup-thumbnail.png
1570 ms
GILCAY516425_CaystonPatientBrochure_2-0page9-refresh.jpg
1688 ms
GILCAY516425_Interactive_CaystonPatientBrochure_5-1_PatientBrochurePRCUpdate_10.jpg
2018 ms
GILCAY516425_Interactive_CaystonPatientBrochure_5-1_PatientBrochurePRCUpdate_11.jpg
1725 ms
GILCAY516425_Interactive_CaystonPatientBrochure_5-1_PatientBrochurePRCUpdate_12.jpg
1784 ms
page13-popup-thumbnail.png
1839 ms
GILCAY516425_Interactive_CaystonPatientBrochure_5-1_PatientBrochurePRCUpdate_13.jpg
2026 ms
GILCAY516425_Interactive_CaystonPatientBrochure_5-1_PatientBrochurePRCUpdate_14.jpg
2174 ms
GILCAY516425_CaystonPatientBrochure_2-0page15-refresh.jpg
3062 ms
GILCAY516425_Interactive_CaystonPatientBrochure_5-1_PatientBrochurePRCUpdate_16.jpg
2313 ms
page17-popup-thumbnail.png
1938 ms
GILCAY516425_CaystonPatientBrochure_2-0page17-refresh.jpg
3100 ms
GILCAY516425_Interactive_CaystonPatientBrochure_5-1_PatientBrochurePRCUpdate_18.jpg
2330 ms
GILCAY516425_CaystonPatientBrochure_2-0page19-refresh.jpg
2398 ms
GILCAY516425_Interactive_CaystonPatientBrochure_5-1_PatientBrochurePRCUpdate_20.jpg
2579 ms
home-hero-2.jpg
2268 ms
9BxXuLjQ1eHankc5PVPyjgUIw==
136 ms
QcV7i40NXh2p5HOT1T8o4FCM=
134 ms
QcV7i40NXh2p5HOT1T8o4FCM=
134 ms
KOBQj
134 ms
QcV7i40NXh2p5HOT1T8o4FCM=
133 ms
KOBQj
132 ms
QcV7i40NXh2p5HOT1T8o4FCM=
132 ms
KOBQj
142 ms
otSDKStub.js
291 ms
564eaab8-f31f-42dc-bcb1-bd197a406783.json
30 ms
location
99 ms
otBannerSdk.js
81 ms
en.json
114 ms
analytics.js
28 ms
otCenterRounded.json
134 ms
otPcTab.json
154 ms
otCommonStyles.css
156 ms
collect
52 ms
collect
208 ms
poweredBy_ot_logo.svg
15 ms
collect
140 ms
collect
67 ms
cayston.com 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
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<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
Image elements do not have [alt] attributes
cayston.com 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
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
cayston.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cayston.com 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 Cayston.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.
cayston.com
Open Graph data is detected on the main page of CAYSTON. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: