3.6 sec in total
174 ms
3.3 sec
138 ms
Click here to check amazing My Access 360 content. Otherwise, check out these important facts you probably never knew about myaccess360.com
The Access 360 program provides personal support to connect patients to affordability programs and streamline access and reimbursement for select AstraZeneca medicines.
Visit myaccess360.comWe analyzed Myaccess360.com page load time and found that the first response time was 174 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
myaccess360.com performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value5.7 s
16/100
25%
Value4.7 s
68/100
10%
Value6,010 ms
0/100
30%
Value0.042
99/100
15%
Value14.7 s
8/100
10%
174 ms
669 ms
4 ms
15 ms
18 ms
Our browser made a total of 78 requests to load all elements on the main page. We found that 62% of them (48 requests) were addressed to the original Myaccess360.com, 24% (19 requests) were made to Use.typekit.net and 6% (5 requests) were made to Tags.tiqcdn.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Myaccess360.com.
Page size can be reduced by 76.0 kB (14%)
528.1 kB
452.1 kB
In fact, the total size of Myaccess360.com main page is 528.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 65% of websites need less resources to load. Javascripts take 318.3 kB which makes up the majority of the site volume.
Potential reduce by 25.4 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. This page needs HTML code to be minified as it can gain 4.6 kB, which is 14% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 25.4 kB or 77% of the original size.
Potential reduce by 29.1 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, My Access 360 needs image optimization as it can save up to 29.1 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 12.7 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 8.7 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. Myaccess360.com needs all CSS files to be minified and compressed as it can save up to 8.7 kB or 14% of the original size.
Number of requests can be reduced by 30 (56%)
54
24
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of My Access 360. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
myaccess360.com
174 ms
www.myaccess360.com
669 ms
jquery.min.js
4 ms
utils.min.js
15 ms
granite.min.js
18 ms
jquery.min.js
20 ms
shared.min.js
20 ms
underscore.min.js
18 ms
kernel.min.js
23 ms
responsive-utils.min.js
34 ms
exitramp.js
31 ms
main.js
33 ms
tool-tip.js
71 ms
jquery.tooltipster.min.js
33 ms
responsive-utils.min.css
71 ms
global.css
79 ms
banner.css
86 ms
gridcallout.css
82 ms
brandcolor.css
83 ms
exit-ramp.css
87 ms
tooltipster.css
87 ms
tooltip-style.css
85 ms
utag.sync.js
88 ms
standard-menu.css
87 ms
autologinsuccessMsgcomponent.min.css
87 ms
autologinsuccessMsgcomponent.min.js
88 ms
token.json
658 ms
tig5thq.css
143 ms
p.css
21 ms
privacyoptions123x59.png
107 ms
1600234684399.png
7 ms
home-download.png
8 ms
home-finance.png
7 ms
home-enroll.png
9 ms
Access360_footer_icon.png
9 ms
link-out-icon-transparent.png
96 ms
azlogo.png
95 ms
utag.js
98 ms
head-repeat.png
601 ms
nav-ipad.png
602 ms
down-arrow.png
600 ms
segmentation.segment.js
641 ms
stores.init.js
683 ms
exit-ramp.html
2121 ms
hcp-home-banner.png
2105 ms
white_arrow.png
2104 ms
arrow-red.jpg
2104 ms
flag-icon.png
2103 ms
search-mob.png
2102 ms
close_button.png
2101 ms
helveticaneueltstd-roman.woff
2104 ms
HelveticaNeueLTStd-Roman.woff
2105 ms
d
28 ms
d
72 ms
d
66 ms
d
115 ms
d
116 ms
d
115 ms
d
132 ms
d
114 ms
d
141 ms
d
118 ms
d
195 ms
d
137 ms
d
181 ms
d
260 ms
d
190 ms
d
175 ms
d
147 ms
d
159 ms
HelveticaNeueLTStd-Bd.woff
2103 ms
utag.23.js
57 ms
utag.3.js
48 ms
ga.js
17 ms
1939c1e0_panel-en-gb.js
133 ms
utag.v.js
8 ms
__utm.gif
23 ms
index.html
4 ms
myaccess360.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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
myaccess360.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
Browser errors were logged to the console
myaccess360.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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Myaccess360.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 Myaccess360.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.
myaccess360.com
Open Graph description is not detected on the main page of My Access 360. 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: