9.1 sec in total
1.7 sec
6.9 sec
564 ms
Welcome to runtofightcancer.com homepage info - get ready to check Run To Fight Cancer best content right away, or after learning these important things about runtofightcancer.com
Run to Fight Children's Cancer 2023 Click Here to Register today! On your mark. Get set. GO! Days Hours Mins Race Starter 2023 >> Meet Elilai! Elilai is 9 years…
Visit runtofightcancer.comWe analyzed Runtofightcancer.com page load time and found that the first response time was 1.7 sec and then it took 7.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
runtofightcancer.com performance score
name
value
score
weighting
Value4.9 s
11/100
10%
Value5.8 s
15/100
25%
Value18.7 s
0/100
10%
Value2,360 ms
5/100
30%
Value0.321
36/100
15%
Value34.9 s
0/100
10%
1689 ms
82 ms
309 ms
304 ms
160 ms
Our browser made a total of 110 requests to load all elements on the main page. We found that 97% of them (107 requests) were addressed to the original Runtofightcancer.com, 1% (1 request) were made to Fonts.googleapis.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Runtofightcancer.com.
Page size can be reduced by 290.2 kB (6%)
4.5 MB
4.2 MB
In fact, the total size of Runtofightcancer.com main page is 4.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. 75% 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 3.8 MB which makes up the majority of the site volume.
Potential reduce by 176.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. 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 176.6 kB or 83% of the original size.
Potential reduce by 112.5 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. Run To Fight Cancer images are well optimized though.
Potential reduce by 400 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 695 B
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. Runtofightcancer.com has all CSS files already compressed.
Number of requests can be reduced by 57 (68%)
84
27
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Run To Fight Cancer. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 36 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
www.runtofightcancer.com
1689 ms
wp-emoji-release.min.js
82 ms
style.min.css
309 ms
all.min.css
304 ms
simple-line-icons.min.css
160 ms
style.min.css
325 ms
hamburgers.min.css
297 ms
3dx-r.css
306 ms
b09e3f3b46e852ac89a054e84500c862.css
238 ms
elementor-icons.min.css
318 ms
frontend-legacy.min.css
368 ms
frontend.min.css
384 ms
swiper.min.css
376 ms
post-2244.css
382 ms
frontend.min.css
427 ms
all.min.css
396 ms
v4-shims.min.css
440 ms
post-355.css
449 ms
post-862.css
460 ms
widgets.css
463 ms
style.min.css
468 ms
css
43 ms
jquery.min.js
510 ms
jquery-migrate.min.js
520 ms
v4-shims.min.js
523 ms
js
79 ms
stream-id2.css
618 ms
animations.min.css
626 ms
imagesloaded.min.js
618 ms
theme.min.js
627 ms
drop-down-mobile-menu.min.js
626 ms
overlay-search.min.js
627 ms
magnific-popup.min.js
628 ms
ow-lightbox.min.js
628 ms
flickity.pkgd.min.js
670 ms
ow-slider.min.js
669 ms
scroll-effect.min.js
670 ms
scroll-top.min.js
693 ms
2b5afad190.js
94 ms
select.min.js
693 ms
main.min.js
621 ms
webpack-pro.runtime.min.js
557 ms
webpack.runtime.min.js
492 ms
frontend-modules.min.js
456 ms
regenerator-runtime.min.js
446 ms
wp-polyfill.min.js
447 ms
hooks.min.js
471 ms
i18n.min.js
465 ms
frontend.min.js
470 ms
waypoints.min.js
458 ms
core.min.js
457 ms
swiper.min.js
473 ms
share-link.min.js
472 ms
dialog.min.js
462 ms
frontend.min.js
482 ms
preloaded-elements-handlers.min.js
603 ms
preloaded-modules.min.js
462 ms
jquery.sticky.min.js
466 ms
rtf-logo.png
453 ms
run2fight-fallback-image.png
2575 ms
DSC00124-1024x850.jpg
530 ms
ccn-white-3.png
405 ms
Phoenix-Childrens-Hospital-logo-ogwotrw3476gmbef1fs607avau4ywi5v79hyh8xyxe.png
329 ms
012.jpg
437 ms
pono-2-1.jpeg
392 ms
Phoenix-ChildrensHospital-Logo.jpg
496 ms
StoneColdMasonry.jpg
414 ms
suntech-concrete.png
439 ms
download.png
437 ms
sole-sports.png
457 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
470 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf
475 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf
562 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf
602 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf
641 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf
512 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf
513 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf
567 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf
581 ms
public.css
568 ms
fa-brands-400.woff
673 ms
fa-brands-400.woff
804 ms
fa-solid-900.woff
664 ms
fa-solid-900.woff
739 ms
fa-regular-400.woff
601 ms
fa-regular-400.woff
647 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjMDrMfJQ.ttf
664 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4VrMDrMfJQ.ttf
666 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4TbMDrMfJQ.ttf
750 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4ejMDrMfJQ.ttf
709 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4WjNDrMfJQ.ttf
687 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4bbLDrMfJQ.ttf
729 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4Y_LDrMfJQ.ttf
750 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4ejLDrMfJQ.ttf
693 ms
1Pt_g8zYS_SKggPNyCgSQamb1W0lwk4S4cHLDrMfJQ.ttf
737 ms
eicons.woff
857 ms
public.js
696 ms
admin-ajax.php
1437 ms
Marlin-Mechanical.jpg
658 ms
Hillys-300x200.jpg
705 ms
AERO_logo.jpg
668 ms
tsr_v_rgb_300dpi.jpg
741 ms
SRMG_100-American_2-Color-1.jpg
705 ms
logo-dealer-f27e92a9b23d68b84731d67c3c08e81a49cb46099d7d62c135a5f084a42cd0f8.png
745 ms
download.jpg
675 ms
download.png
675 ms
oval.svg
80 ms
video.png
82 ms
flaticon.svg
263 ms
flaticon.svg
165 ms
runtofightcancer.com 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.
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
Links do not have a discernible name
runtofightcancer.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
runtofightcancer.com 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 Runtofightcancer.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 Runtofightcancer.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.
runtofightcancer.com
Open Graph data is detected on the main page of Run To Fight Cancer. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: