5.2 sec in total
1.2 sec
3.6 sec
439 ms
Welcome to sanctionswiki.org homepage info - get ready to check Sanctionswiki best content for United States right away, or after learning these important things about sanctionswiki.org
Sanctions Wiki -
Visit sanctionswiki.orgWe analyzed Sanctionswiki.org page load time and found that the first response time was 1.2 sec and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
sanctionswiki.org performance score
name
value
score
weighting
Value3.7 s
30/100
10%
Value4.3 s
43/100
25%
Value7.5 s
27/100
10%
Value3,680 ms
1/100
30%
Value0.236
53/100
15%
Value14.3 s
9/100
10%
1156 ms
127 ms
490 ms
236 ms
414 ms
Our browser made a total of 73 requests to load all elements on the main page. We found that 86% of them (63 requests) were addressed to the original Sanctionswiki.org, 4% (3 requests) were made to Platform.twitter.com and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Sanctionswiki.org.
Page size can be reduced by 253.8 kB (29%)
887.7 kB
633.9 kB
In fact, the total size of Sanctionswiki.org main page is 887.7 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. 35% of websites need less resources to load. Images take 585.5 kB which makes up the majority of the site volume.
Potential reduce by 136.8 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 136.8 kB or 80% of the original size.
Potential reduce by 47.1 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. Sanctionswiki images are well optimized though.
Potential reduce by 50.4 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 50.4 kB or 47% of the original size.
Potential reduce by 19.6 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. Sanctionswiki.org needs all CSS files to be minified and compressed as it can save up to 19.6 kB or 84% of the original size.
Number of requests can be reduced by 25 (35%)
72
47
The browser has sent 72 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Sanctionswiki. 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 from 4 to 1 for CSS and as a result speed up the page load time.
sanctionswiki.org
1156 ms
CategoryTree.css
127 ms
load.php
490 ms
main-ltr.css
236 ms
load.php
414 ms
widgets.js
12 ms
load.php
428 ms
CategoryTree.js
235 ms
load.php
386 ms
page.js
13 ms
share_save_171_16.png
586 ms
page-base.png
146 ms
page-fade.png
145 ms
border.png
122 ms
bullet-icon.png
121 ms
external-link-ltr-icon.png
149 ms
user-icon.png
150 ms
tab-break.png
203 ms
tab-current-fade.png
201 ms
tab-normal-fade.png
259 ms
arrow-down-icon.png
253 ms
wiki_logo.png
277 ms
portal-break.png
259 ms
ofac-sdnsearch.png
418 ms
un-council.png
423 ms
unhcr.png
561 ms
eeas.png
474 ms
hm-treasury.png
482 ms
AFU.png
391 ms
treasury.png
622 ms
bis.png
625 ms
fincen.png
639 ms
itar.png
580 ms
canada.png
591 ms
dfat.png
658 ms
mfat.png
684 ms
seco.png
695 ms
norway.png
729 ms
mofajapan.png
722 ms
mas.png
740 ms
honkong.png
769 ms
fatfgafi.png
797 ms
oecd.png
916 ms
ibis.png
828 ms
wolfsberg-2.png
840 ms
egmont.png
778 ms
15px-Icons-mini-file_acrobat.gif
99 ms
88x31.png
107 ms
sipri.png
759 ms
transparency.png
787 ms
load.php
1070 ms
hrw.png
801 ms
globalwitness.png
816 ms
warchild.png
826 ms
wassenaar.png
873 ms
exportcontrol.png
839 ms
thetradewiki.png
844 ms
ess.png
818 ms
itn.png
811 ms
criticalthreats.png
879 ms
equasis.png
867 ms
vesseltracker.png
751 ms
worldcheck.png
762 ms
poweredby_mediawiki_88x31.png
773 ms
smw_button.png
781 ms
load.php
485 ms
ga.js
17 ms
sm13.html
54 ms
button.0308b81ff1714e446f674b5b9793f2cd.js
41 ms
lock-icon.png
115 ms
__utm.gif
19 ms
ga.js
41 ms
follow_button.b9740740e0bcf9b0657c5b11bd4388da.en.html
26 ms
sanctionswiki.org accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[aria-*] attributes do not match their roles
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
sanctionswiki.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
sanctionswiki.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sanctionswiki.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 Sanctionswiki.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.
sanctionswiki.org
Open Graph description is not detected on the main page of Sanctionswiki. 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: