11.3 sec in total
124 ms
10.7 sec
504 ms
Visit cancercongress.org now to see the best up-to-date Cancer Congress content and also check out these interesting facts you probably never knew about cancercongress.org
On the Tremendous success of seven editions, We are organizing the 8th World Congress on Cancer Research & Therapy on June 20-22,2024 in the beautiful city of Prague, Czech Republic. This is a global ...
Visit cancercongress.orgWe analyzed Cancercongress.org page load time and found that the first response time was 124 ms and then it took 11.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
cancercongress.org performance score
name
value
score
weighting
Value8.5 s
0/100
10%
Value8.8 s
1/100
25%
Value11.7 s
4/100
10%
Value620 ms
48/100
30%
Value0
100/100
15%
Value12.9 s
13/100
10%
124 ms
304 ms
942 ms
470 ms
198 ms
Our browser made a total of 144 requests to load all elements on the main page. We found that 84% of them (121 requests) were addressed to the original Cancercongress.org, 10% (14 requests) were made to Embed.tawk.to and 2% (3 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (4.4 sec) belongs to the original domain Cancercongress.org.
Page size can be reduced by 1.8 MB (24%)
7.3 MB
5.6 MB
In fact, the total size of Cancercongress.org main page is 7.3 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 6.7 MB which makes up the majority of the site volume.
Potential reduce by 104.6 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 45.5 kB, which is 38% 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 104.6 kB or 88% of the original size.
Potential reduce by 1.6 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. Obviously, Cancer Congress needs image optimization as it can save up to 1.6 MB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 33.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 7.9 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. Cancercongress.org has all CSS files already compressed.
Number of requests can be reduced by 49 (37%)
132
83
The browser has sent 132 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cancer Congress. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
cancercongress.org
124 ms
cancercongress.org
304 ms
responsive-innovinc.css
942 ms
owl.carousel.css
470 ms
bootstrap.css
198 ms
Styles.css
208 ms
jquery.bxslider.css
207 ms
animate.css
942 ms
font-awesome.min.css
1979 ms
font-awesome.min.css
54 ms
responsive.css
1964 ms
custom.css
1972 ms
plugins.css
1980 ms
style.css
3006 ms
jquery.classycountdown.css
3018 ms
aos.css
64 ms
image001.gif
3028 ms
1719317320.jpg
3035 ms
1719317520.jpg
3022 ms
1706000006.jpg
3028 ms
email-decode.min.js
2978 ms
aos.js
46 ms
owl.carousel.min.css
57 ms
owl.theme.min.css
55 ms
jquery.countdown.min.js
3161 ms
jquery.js
3635 ms
plugins.js
4029 ms
jquery-1.12.0.min.js
48 ms
owl.carousel.min.js
60 ms
functions.js
4067 ms
bootstrap.min.js
4066 ms
jquery.bxslider.js
4081 ms
TimeCircles.js
4082 ms
resize.js
4085 ms
jquery.fittext.js
4212 ms
jquery.lettering.js
4222 ms
jquery.textillate.js
4222 ms
jquery.easing.min.js
4227 ms
mainScripts.js
4224 ms
main.js
4228 ms
scrolla.jquery.min.js
4383 ms
scripts.js
4392 ms
css
35 ms
locate-icon.png
1675 ms
title-bg.png
1678 ms
arrow-list.png
1679 ms
1678970868.jpg
1732 ms
1705931166.png
2005 ms
1705931670.jpg
2178 ms
1710580734.jpg
2045 ms
1705900678.jpg
2214 ms
1721384598.jpg
2231 ms
1677587479.jpg
2241 ms
1677587883.jpg
2243 ms
1723630487.jpg
2291 ms
1702275745.jpg
2350 ms
1702275849.jpg
2386 ms
1702993432.jpg
2402 ms
1703164825.jpg
2415 ms
1711434629.jpeg
2413 ms
1702276361.jfif
2468 ms
1702276496.png
2524 ms
1702276620.jpg
2557 ms
fontawesome-webfont.woff
28 ms
fontawesome-webfont.woff
2606 ms
1hhm2678o
83 ms
fontawesome-webfont.woff
1988 ms
1702276750.png
1537 ms
1684219332.jpg
1581 ms
1706772211.jpg
1625 ms
1708091283.jpg
1653 ms
1708666723.jpg
1689 ms
1709272378.jpg
1729 ms
1710241249.jpg
1612 ms
1710567485.jpg
1660 ms
1711013210.PNG
1683 ms
1712061726.jpg
1722 ms
1712062757.jpg
1731 ms
1712062794.jpg
1824 ms
1712914978.jpg
1610 ms
default
285 ms
1713345588.png
1370 ms
1714121750.jpg
1395 ms
1714122017.jpg
1432 ms
1714743596.jpg
1445 ms
1714981173.png
1441 ms
1714981222.jpg
1207 ms
1715164548.jpg
1168 ms
1715850115.png
955 ms
1715850170.jpg
1065 ms
1716197360.jpg
1066 ms
1716197404.png
1660 ms
1716275842.jfif
991 ms
1716532985.jpg
1623 ms
1717069529.jpg
1657 ms
1717069559.jpg
1640 ms
1717072882.jfif
1621 ms
1718100951.jpg
1611 ms
1690971842.jpg
2504 ms
1667380628.png
2465 ms
1690971147.jpg
2532 ms
1690971290.jpg
2503 ms
1690971392.jpg
2469 ms
1690971570.jpg
2416 ms
1690971621.png
2578 ms
fontawesome-webfont.ttf
3059 ms
1690971668.jpg
3224 ms
1690971783.jpg
3191 ms
1690972005.jpg
2951 ms
1690972148.jpg
3142 ms
1721738222.jpg
3142 ms
1721738332.jpg
3256 ms
1721738432.jpg
3255 ms
1721738534.jpg
3218 ms
1721738598.jpg
3358 ms
1721738771.jpg
3167 ms
1722951203.jpg
3110 ms
1722951161.jpg
3274 ms
1722950838.jpg
3261 ms
1722950814.jpg
3216 ms
1722950794.jpg
3201 ms
1721718639.jpeg
3187 ms
1721718589.jpg
3311 ms
1720604536.JPG
3535 ms
1611379992.png
3278 ms
1611382038.jpg
3257 ms
1611382049.jpg
3511 ms
1611382075.png
3538 ms
1674200785.png
2937 ms
1674218335.png
3061 ms
title-bg.png
3041 ms
fontawesome-webfont.svg
1228 ms
twk-arr-find-polyfill.js
60 ms
twk-object-values-polyfill.js
81 ms
twk-event-polyfill.js
175 ms
twk-entries-polyfill.js
71 ms
twk-iterator-polyfill.js
90 ms
twk-promise-polyfill.js
176 ms
twk-main.js
73 ms
twk-vendor.js
84 ms
twk-chunk-vendors.js
96 ms
twk-chunk-common.js
112 ms
twk-runtime.js
112 ms
twk-app.js
113 ms
cancercongress.org 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
Image elements do not have [alt] attributes
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
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
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
cancercongress.org 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
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
cancercongress.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cancercongress.org 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 Cancercongress.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.
cancercongress.org
Open Graph description is not detected on the main page of Cancer Congress. 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: