2.7 sec in total
325 ms
2.1 sec
241 ms
Click here to check amazing CITES content for United States. Otherwise, check out these important facts you probably never knew about cites.org
Visit cites.orgWe analyzed Cites.org page load time and found that the first response time was 325 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
cites.org performance score
name
value
score
weighting
Value2.3 s
75/100
10%
Value11.1 s
0/100
25%
Value6.7 s
36/100
10%
Value330 ms
76/100
30%
Value0
100/100
15%
Value9.9 s
27/100
10%
325 ms
420 ms
96 ms
190 ms
279 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 96% of them (45 requests) were addressed to the original Cites.org, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (789 ms) belongs to the original domain Cites.org.
Page size can be reduced by 308.1 kB (40%)
779.5 kB
471.4 kB
In fact, the total size of Cites.org main page is 779.5 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. 30% of websites need less resources to load. Images take 374.7 kB which makes up the majority of the site volume.
Potential reduce by 42.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 42.6 kB or 79% of the original size.
Potential reduce by 3.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. CITES images are well optimized though.
Potential reduce by 188.1 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 188.1 kB or 72% of the original size.
Potential reduce by 73.8 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. Cites.org needs all CSS files to be minified and compressed as it can save up to 73.8 kB or 81% of the original size.
Number of requests can be reduced by 18 (40%)
45
27
The browser has sent 45 CSS, Javascripts, AJAX and image requests in order to completely render the main page of CITES. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
cites.org
325 ms
cites.org
420 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
96 ms
css_vZ_wrMQ9Og-YPPxa1q4us3N7DsZMJa-14jShHgRoRNo.css
190 ms
css_pXEMln-qzvHtMZkjoYWkvWHFfAQa_RUOxo9vqnuCZd4.css
279 ms
css_GMefWd_y4CuOY-VZPKjgnaDCQOSz7fGAsZp5SkN6ZfA.css
280 ms
css_9YjYPSsnoCf8fosgfS7NiX_BtnF-7swFNyA3wz23V8s.css
282 ms
css_o0GjmntdV0yNpAUq9bG0jUz3JRsHD8wsIsMR1ZhDbP8.css
285 ms
js_MG2mAeTPw6UhklY_SgV9St7ugWHPu3aFJezoNDTlCOA.js
471 ms
js_ET8tWt_GfTsIhn5mbHHqsaa6Qxx4G1Ja0ZYtIpHaOfY.js
293 ms
js_nFUwq93Kf3Re00iyVU2giw3JAqA2cMG0wpQwKiqGlp4.js
460 ms
js_EvbDNFWpjY9G6yRGH-oO3XbsNlK3lLxV3SupOnvtv8g.js
370 ms
js_TlAQHrlUXoEaMEdfgNLwh_jPgONGdnU4RozSgQ1eVqY.js
371 ms
analytics.js
88 ms
page-wrapper.gif
104 ms
page.gif
101 ms
header-en.jpg
192 ms
main-menu.gif
100 ms
search-icon-light.png
102 ms
search-button.png
101 ms
arrow-right-black.gif
192 ms
sidebar-second.gif
194 ms
arrow-right-green.gif
198 ms
VC.gif
199 ms
ani_dashboards.gif
198 ms
inforMEA.gif
284 ms
content-title.jpg
284 ms
wwd2016.jpg
507 ms
sri_lanka2.jpg
601 ms
sc66_page3_slider.gif
522 ms
sc66_s.gif
507 ms
CITES-slide-hp_0.jpg
701 ms
bullets.png
383 ms
facebook-sm.png
476 ms
flickr-sm.png
569 ms
twitter-sm.png
602 ms
youtube-sm.png
604 ms
sidebar-second-title.gif
616 ms
cop17_highlightv2.jpg
751 ms
livelihoods_home_2.gif
697 ms
home_iccwc.jpg
695 ms
cites_legislation.jpg
698 ms
shark_ray_t.jpg
720 ms
arrow-right-orange.gif
788 ms
footer.gif
789 ms
collect
11 ms
css_hCL0cQlce22GKIaxJhAomqKygvJd2rqsvvbSWuDOfuU.css
96 ms
cites.org 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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
cites.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
cites.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Image elements do not have [alt] attributes
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 Cites.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 Cites.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.
cites.org
Open Graph description is not detected on the main page of CITES. 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: