3.2 sec in total
1.3 sec
1.8 sec
92 ms
Click here to check amazing Cancer52 content. Otherwise, check out these important facts you probably never knew about cancer52.org.uk
Cancer52 is an alliance of over 90 organisations, united in improving the future for everyone affected by rare and less common cancers.
Visit cancer52.org.ukWe analyzed Cancer52.org.uk page load time and found that the first response time was 1.3 sec and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
cancer52.org.uk performance score
name
value
score
weighting
Value2.3 s
73/100
10%
Value14.2 s
0/100
25%
Value7.7 s
25/100
10%
Value2,370 ms
5/100
30%
Value0.184
66/100
15%
Value13.3 s
12/100
10%
1274 ms
23 ms
70 ms
72 ms
5 ms
Our browser made a total of 30 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Cancer52.org.uk, 63% (19 requests) were made to Static.parastorage.com and 20% (6 requests) were made to Static.wixstatic.com. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Cancer52.org.uk.
Page size can be reduced by 399.1 kB (68%)
589.3 kB
190.3 kB
In fact, the total size of Cancer52.org.uk main page is 589.3 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. 50% of websites need less resources to load. HTML takes 496.6 kB which makes up the majority of the site volume.
Potential reduce by 388.5 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 388.5 kB or 78% of the original size.
Potential reduce by 10.6 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, Cancer52 needs image optimization as it can save up to 10.6 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 48 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.
Number of requests can be reduced by 9 (41%)
22
13
The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cancer52. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and as a result speed up the page load time.
www.cancer52.org.uk
1274 ms
minified.js
23 ms
focus-within-polyfill.js
70 ms
polyfill.min.js
72 ms
bootstrap-features.24d4529b.bundle.min.js
5 ms
main.24eb524d.bundle.min.js
8 ms
lodash.min.js
15 ms
react.production.min.js
33 ms
siteTags.bundle.min.js
32 ms
thunderbolt
142 ms
wix-perf-measure.bundle.min.js
108 ms
react-dom.production.min.js
109 ms
Cancer52sitelogo_edited.png
256 ms
962cfeae07cd4095bcdbff04e476d97b.png
335 ms
e22361_a64cc95544cc46b4937621119a014fe7~mv2_d_3184_1559_s_2.jpg
447 ms
e22361_d5a4ba24b50a456498c97ff48a80abfb~mv2_d_3816_1684_s_2.jpg
464 ms
e22361_bc9daa82f3db408390d886d50527cacb~mv2_d_6250_2583_s_4_2.png
400 ms
e22361_93842622bd094b3099a2a15f28a8ee3d~mv2.png
487 ms
thunderbolt
29 ms
03805817-4611-4dbc-8c65-0f73031c3973.woff
18 ms
80c34ad2-27c2-4d99-90fa-985fd64ab81a.woff
18 ms
c5749443-93da-4592-b794-42f28d62ef72.woff
28 ms
192dac76-a6d9-413d-bb74-22308f2e0cc5.woff
30 ms
0a3939d0-3833-4db3-8b85-f64c2b3350d2.woff
30 ms
e56ecb6d-da41-4bd9-982d-2d295bec9ab0.woff
30 ms
ProximaNovaW05-Regular.woff
30 ms
deprecation-en.v5.html
11 ms
bolt-performance
53 ms
deprecation-style.v5.css
10 ms
right-arrow.svg
9 ms
cancer52.org.uk accessibility score
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
cancer52.org.uk 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
Page has valid source maps
cancer52.org.uk 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cancer52.org.uk 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 Cancer52.org.uk 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.
cancer52.org.uk
Open Graph data is detected on the main page of Cancer52. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: