6.8 sec in total
84 ms
6 sec
798 ms
Click here to check amazing Yesits Genocide content. Otherwise, check out these important facts you probably never knew about yesitsgenocide.com
Dear President Biden, It is time for the White House to unequivocally affirm official U.S. policy established in a near unanimous historic bipartisan expression by Congress in H.Res.296 and S.Res.150 ...
Visit yesitsgenocide.comWe analyzed Yesitsgenocide.com page load time and found that the first response time was 84 ms and then it took 6.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
yesitsgenocide.com performance score
name
value
score
weighting
Value2.5 s
68/100
10%
Value4.9 s
29/100
25%
Value5.6 s
52/100
10%
Value37,980 ms
0/100
30%
Value0.004
100/100
15%
Value48.1 s
0/100
10%
84 ms
174 ms
394 ms
1045 ms
488 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Yesitsgenocide.com, 89% (70 requests) were made to Change.org and 4% (3 requests) were made to Browser-update.org. The less responsive or slowest element that took the longest time to load (4.3 sec) relates to the external source Assets.change.org.
Page size can be reduced by 127.2 kB (46%)
277.3 kB
150.1 kB
In fact, the total size of Yesitsgenocide.com main page is 277.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. 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. HTML takes 157.5 kB which makes up the majority of the site volume.
Potential reduce by 125.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. 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 125.0 kB or 79% 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. Yesits Genocide images are well optimized though.
Potential reduce by 2.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. This website has mostly compressed JavaScripts.
Number of requests can be reduced by 68 (94%)
72
4
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yesits Genocide. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 69 to 1 for JavaScripts and as a result speed up the page load time.
yesitsgenocide.com
84 ms
yes-its-genocide
174 ms
president-of-the-united-states-urging-president-biden-to-recognize-the-armenian-genocide
394 ms
urging-president-biden-to-recognize-the-armenian-genocide
1045 ms
main.min.js
488 ms
ywwocnmleixghUW-800x450-noPad.jpg
4266 ms
runtime.4186944e3066fee87b7b.js
424 ms
error~main.d81692a0826d9d0e0b56.js
493 ms
error~main.ae103afbc50f5bab9119.js
590 ms
error~main.a9a71e49394e7be45bc3.js
469 ms
error~main.41f294f733599005e94a.js
461 ms
error~main.8ab57553623966467a53.js
483 ms
error~main.687dcb0042aa8e57a4ab.js
577 ms
error~main.39eb061012a696afd0d0.js
752 ms
error~main.4489f8c7d13a0a61e839.js
737 ms
error~main.5c0c3a3291666f13eda5.js
723 ms
error~main.561510ec2caec90aa14e.js
736 ms
error~main.f42019f25b996ce75440.js
724 ms
error~main.42b3f4b4a2d4ae9a640e.js
749 ms
error~main.d260e5e000347e5ea5c3.js
800 ms
error~main.dd84cd8840a1203f99eb.js
792 ms
error~main.4642bd55e2348370357e.js
793 ms
error~main.75de7426116016d3da56.js
802 ms
error~main.2f765804159feba7c935.js
809 ms
error~main.71e6164e0d811adacbe1.js
812 ms
error~main.9d92532fcbec019de014.js
825 ms
error~main.dce1833527edcb4fb5af.js
822 ms
error~main.8762d6ddfc2b05cdd1cd.js
827 ms
error~main.6b4a5fe603acbfa50464.js
958 ms
error~main.d67e06b82bae2736dbc4.js
963 ms
error~main.c56c26555507a583e564.js
958 ms
error~main.64a8ad937d7000355d86.js
981 ms
error~main.b55685bb3b9db396c2ed.js
969 ms
error~main.7853ade131810e4781b1.js
979 ms
error~main.2f827a6160da46914bfa.js
976 ms
error~main.b49df717aad7e0dd4224.js
981 ms
error~main.ca65153d358e41e42e37.js
990 ms
error~main.41ed152b7199542bc5ba.js
984 ms
error~main.a677e24ff9120c33a491.js
991 ms
error~main.bb687416f795d14a0724.js
1002 ms
error~main.b0b45f97f4dacc9efe8d.js
999 ms
update.min.js
743 ms
qBgtYxPIkvoPtei-48x48-noPad.jpg
3955 ms
Change-Calibre-Regular.woff
672 ms
Change-Calibre-Bold.woff
631 ms
webapp-info~error~main.c149403d78057aae7366.js
883 ms
main.ae9d3761f8442e213bb3.js
588 ms
main.6c5b747bb4de6279fe1c.js
561 ms
main.69c646688892857a0ac6.js
550 ms
main.6b4e02c64aac5e0bd495.js
543 ms
main.478902e927e1ff36e875.js
458 ms
main.977ab1d0a6fff6e5cc97.js
456 ms
main.c47a2b77e2ef1bf59d5a.js
325 ms
main.239f71b1c691bf5b8cce.js
304 ms
main.520f53d2aba6db89c9a1.js
295 ms
main.22e17ff062e7d3636231.js
299 ms
main.7909a397a5c7524970a5.js
297 ms
main.04125886c0ce95545751.js
281 ms
main.923eca0b3b7e97828e3a.js
263 ms
main.0f2477f3e7693a6ed40f.js
239 ms
error~main.91fcbe36fa6127cf2cc4.js
250 ms
main.ff9d8545a79608217dcd.js
245 ms
other.0ecf1a53f1054b285465.js
240 ms
other.e4e01ca273722f06d72e.js
247 ms
other.07b28532dcef22f71e8f.js
229 ms
petition.5f97282e4af581f5ab88.js
225 ms
other.6ea615986ceb1c51c97e.js
225 ms
update.show.min.js
137 ms
other.4afb6d6f155e4ad5a216.js
3154 ms
other.aaeb418b011cfc5e54d7.js
3133 ms
other.985b720f709a23d3afff.js
3131 ms
other.c80135a7d40598730b84.js
3143 ms
other.55c6475abdff8c68c949.js
3116 ms
other.07f683af6e4a27c55259.js
3134 ms
other.9910cd1c1b138c330cc6.js
3131 ms
other.29f20d422b23e557a9e0.js
3132 ms
other.df8bb73031b8f302b661.js
3129 ms
other.43d76fb54c6c61231c4c.js
3125 ms
f.png
260 ms
yesitsgenocide.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.
yesitsgenocide.com 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
yesitsgenocide.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yesitsgenocide.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 Yesitsgenocide.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.
yesitsgenocide.com
Open Graph data is detected on the main page of Yesits Genocide. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: