4.6 sec in total
656 ms
3.6 sec
402 ms
Click here to check amazing Wwf content for Russia. Otherwise, check out these important facts you probably never knew about wwf.ru
Visit wwf.ruWe analyzed Wwf.ru page load time and found that the first response time was 656 ms 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.
wwf.ru performance score
name
value
score
weighting
Value2.7 s
59/100
10%
Value16.7 s
0/100
25%
Value12.3 s
3/100
10%
Value3,290 ms
2/100
30%
Value0.083
93/100
15%
Value16.8 s
5/100
10%
656 ms
278 ms
400 ms
404 ms
273 ms
Our browser made a total of 90 requests to load all elements on the main page. We found that 49% of them (44 requests) were addressed to the original Wwf.ru, 14% (13 requests) were made to Vk.com and 6% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Wwf.ru.
Page size can be reduced by 633.0 kB (34%)
1.9 MB
1.2 MB
In fact, the total size of Wwf.ru main page is 1.9 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. 45% of websites need less resources to load. Images take 989.2 kB which makes up the majority of the site volume.
Potential reduce by 34.7 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 34.7 kB or 74% of the original size.
Potential reduce by 25.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. Wwf images are well optimized though.
Potential reduce by 463.0 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 463.0 kB or 65% of the original size.
Potential reduce by 109.7 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. Wwf.ru needs all CSS files to be minified and compressed as it can save up to 109.7 kB or 82% of the original size.
Number of requests can be reduced by 45 (54%)
84
39
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wwf. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
wwf.ru
656 ms
structure.css
278 ms
elements.css
400 ms
jquery-ui-1.8.2.custom.css
404 ms
spotlight.css
273 ms
mainpage.css
270 ms
jquery-1.7.1.min.js
777 ms
jquery-ui-1.8.18.custom.min.js
1162 ms
jquery.json-1.3.min.js
536 ms
jquery.lb-video-map.halfpacked.js
688 ms
service.js
658 ms
sharer.js
662 ms
spotlight.js
796 ms
style.css
826 ms
openapi.js
505 ms
fonts.css
646 ms
print.css
166 ms
gtm.js
113 ms
main-menu-background-not-active.png
147 ms
logo_sup.gif
294 ms
all.js
82 ms
wwfru.ttf
679 ms
hqdefault.jpg
244 ms
dji_0016_up.spotbig.jpg
664 ms
bg_transparent_black.png
291 ms
stories_nav_up.png
422 ms
dji_0016_up.spotthm.jpg
422 ms
spotpolar1.spotthm.jpg
526 ms
spotpolar1.spotbig.jpg
821 ms
pandaspot.spotthm.jpg
658 ms
pandaspot.spotbig.jpg
1093 ms
stories_nav_down.png
820 ms
0030--diego-lopez-wwf.mnews.jpg
921 ms
web_233626.mnews.jpg
923 ms
direktor-tsentra-amurskii-tigr-yrii-birykov-i--direktor-wwf-rossii-igor-chestin.mnews.jpg
970 ms
dalnevostochnyi-aist---simvol-amura_avtor-foto-yrii-gafarov_1.mnews.jpg
1088 ms
know_more2.png
1090 ms
test_pop_panda.jpg
1620 ms
hz3.superwidefeature.jpg
1192 ms
qiwi-widget.superwidefeature.jpg
1214 ms
widgetpanda1.superwidefeature.jpg
1350 ms
lapka.superwidefeature.jpg
1351 ms
icons.png
1355 ms
darkbuttonshadow.png
1482 ms
iframe_api
58 ms
magnify.cur
1491 ms
upload.gif
196 ms
widget_community.php
319 ms
watch.js
1 ms
ga.js
36 ms
orpho.js
1571 ms
all.js
317 ms
restserver.php
135 ms
count.json
22 ms
share.php
274 ms
close_fancy.png
1561 ms
jquery.min.js
171 ms
__utm.gif
67 ms
analytics.js
48 ms
gtm.js
69 ms
www-widgetapi.js
108 ms
collect
46 ms
collect
105 ms
suggest.js
42 ms
opensearch.js
48 ms
ga-audiences
53 ms
loader_nav19239_3.js
140 ms
lite.css
134 ms
lite.js
422 ms
lang3_0.js
256 ms
widget_community.css
271 ms
xdm.js
257 ms
al_community.js
267 ms
97 ms
xd_arbiter.php
221 ms
xd_arbiter.php
445 ms
pixel
25 ms
pixel
18 ms
sync
324 ms
cyR-LWkOPNc.jpg
399 ms
MDYw-0NucOk.jpg
281 ms
BTRVyoFOrcI.jpg
279 ms
_ru5-o4PAkw.jpg
410 ms
wKt7vWFzMOA.jpg
278 ms
FlE5X36eftc.jpg
413 ms
cIsSfrguKCs.jpg
278 ms
camera_50.png
125 ms
w_logo.png
147 ms
mobile_test.css
133 ms
collect
29 ms
wwf.ru 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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
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
wwf.ru 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
Missing source maps for large first-party JavaScript
wwf.ru SEO score
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
Tap targets are not sized appropriately
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wwf.ru can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 Wwf.ru 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.
wwf.ru
Open Graph description is not detected on the main page of Wwf. 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: