1.5 sec in total
114 ms
1.1 sec
255 ms
Welcome to greatlakescancercare.org homepage info - get ready to check Great Lakes Cancer Care best content right away, or after learning these important things about greatlakescancercare.org
Our strength comes from our nurses, doctors and specialists, from many of WNY's top cancer care providers, collaborating to help you through your unique challenges.
Visit greatlakescancercare.orgWe analyzed Greatlakescancercare.org page load time and found that the first response time was 114 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.
greatlakescancercare.org performance score
name
value
score
weighting
Value3.0 s
51/100
10%
Value6.2 s
11/100
25%
Value3.0 s
94/100
10%
Value920 ms
30/100
30%
Value0.159
73/100
15%
Value7.1 s
52/100
10%
114 ms
157 ms
68 ms
85 ms
54 ms
Our browser made a total of 56 requests to load all elements on the main page. We found that 23% of them (13 requests) were addressed to the original Greatlakescancercare.org, 13% (7 requests) were made to Use.typekit.net and 7% (4 requests) were made to Live.rezync.com. The less responsive or slowest element that took the longest time to load (283 ms) relates to the external source Use.typekit.net.
Page size can be reduced by 30.7 kB (7%)
432.2 kB
401.5 kB
In fact, the total size of Greatlakescancercare.org main page is 432.2 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. 25% of websites need less resources to load. Images take 346.8 kB which makes up the majority of the site volume.
Potential reduce by 16.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. This page needs HTML code to be minified as it can gain 3.1 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 16.0 kB or 74% of the original size.
Potential reduce by 0 B
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. Great Lakes Cancer Care images are well optimized though.
Potential reduce by 10.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 10.2 kB or 34% of the original size.
Potential reduce by 4.5 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. Greatlakescancercare.org needs all CSS files to be minified and compressed as it can save up to 4.5 kB or 13% of the original size.
Number of requests can be reduced by 29 (71%)
41
12
The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Great Lakes Cancer Care. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and as a result speed up the page load time.
www.greatlakescancercare.org
114 ms
js
157 ms
tbk7sxy.css
68 ms
6e9d968e25.js
85 ms
styles.css
54 ms
vue@2.6.11
48 ms
modernizr-custom.js
78 ms
jquery-3.5.0.min.js
44 ms
popper.min.js
48 ms
bootstrap.min.js
51 ms
custom.js
81 ms
call.js
81 ms
header.js
82 ms
footer.js
82 ms
outage.js
181 ms
p.css
22 ms
tc.min.js
240 ms
ktag.js
240 ms
gtm.js
67 ms
hero-home-wide.jpg
237 ms
v1
244 ms
COC-logo.jpg
198 ms
side-bucket-team-rev.jpg
199 ms
side-bucket-man.jpg
199 ms
cta-home.jpg
243 ms
GLHCC-logo.svg
196 ms
v1
207 ms
v1
206 ms
d
51 ms
d
41 ms
d
283 ms
d
31 ms
d
50 ms
d
25 ms
ca.html
137 ms
pixel
212 ms
pixel
146 ms
Pug
165 ms
cksync.php
205 ms
194 ms
360947.gif
172 ms
rocketfuel_sync
231 ms
sync
150 ms
g.pixel
152 ms
demconf.jpg
17 ms
sd
9 ms
pixel
20 ms
bounce
30 ms
cm
9 ms
rum
23 ms
sync
15 ms
pixel
76 ms
pixel
70 ms
pixel
70 ms
sync
49 ms
sync
34 ms
greatlakescancercare.org 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.
greatlakescancercare.org 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
greatlakescancercare.org 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Greatlakescancercare.org 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 Greatlakescancercare.org 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.
greatlakescancercare.org
Open Graph description is not detected on the main page of Great Lakes Cancer Care. 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: