10.2 sec in total
1.3 sec
8.5 sec
388 ms
Visit 64hex.ru now to see the best up-to-date 64 Hex content for United States and also check out these interesting facts you probably never knew about 64hex.ru
Китайская Книга перемен И цзин - значения гексаграмм из книг популярных авторов.
Visit 64hex.ruWe analyzed 64hex.ru page load time and found that the first response time was 1.3 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
64hex.ru performance score
name
value
score
weighting
Value3.0 s
48/100
10%
Value15.0 s
0/100
25%
Value7.2 s
30/100
10%
Value1,450 ms
15/100
30%
Value0.391
26/100
15%
Value15.3 s
7/100
10%
1312 ms
309 ms
373 ms
313 ms
280 ms
Our browser made a total of 54 requests to load all elements on the main page. We found that 11% of them (6 requests) were addressed to the original 64hex.ru, 20% (11 requests) were made to Vk.com and 19% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (4.7 sec) relates to the external source Vk.com.
Page size can be reduced by 365.1 kB (64%)
569.1 kB
204.0 kB
In fact, the total size of 64hex.ru main page is 569.1 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. Javascripts take 225.3 kB which makes up the majority of the site volume.
Potential reduce by 149.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 149.6 kB or 88% of the original size.
Potential reduce by 3.2 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. 64 Hex images are well optimized though.
Potential reduce by 174.6 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 174.6 kB or 77% of the original size.
Potential reduce by 37.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. 64hex.ru needs all CSS files to be minified and compressed as it can save up to 37.7 kB or 81% of the original size.
Number of requests can be reduced by 19 (39%)
49
30
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 64 Hex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
64hex.ru
1312 ms
source.css
309 ms
openapi.js
373 ms
style.css
313 ms
all.js
280 ms
22.jpg
542 ms
logo.jpg
469 ms
2478.gif
479 ms
context.js
230 ms
context_static_r1084.js
334 ms
84487
159 ms
watch.js
0 ms
y90
172 ms
y90
246 ms
upload.gif
1168 ms
dot.gif
162 ms
widget_community.php
1241 ms
198 ms
hit
267 ms
xd_arbiter.php
267 ms
xd_arbiter.php
515 ms
like_box.php
186 ms
hit
157 ms
4zvF1Y0eZKv.css
316 ms
FrSU6IlfEX1.css
392 ms
SRSW8M763HA.js
533 ms
4uFOsJeWEIM.js
661 ms
y97Ig99UVTs.js
528 ms
KHAtULXOQuz.js
553 ms
575794_261049283990910_145241438_n.jpg
300 ms
1798753_1465810110297437_2057681417_n.jpg
365 ms
1962875_574513185974213_1820596785_n.jpg
440 ms
12509402_113351809045133_6979811180041502364_n.jpg
509 ms
wL6VQj7Ab77.png
79 ms
1JLnMyDN79z.png
82 ms
loader_nav19239_3.js
190 ms
lite.css
497 ms
lite.js
758 ms
lang3_0.js
910 ms
widget_community.css
1042 ms
xdm.js
1163 ms
al_community.js
4727 ms
VXcANLwwL5J.js
72 ms
i8XO-4kv8i7.js
84 ms
3fTpNsiNRPq40000gK6EkRz-S0M5bw0Kdhn40004kltsWVv_ehg0196s75D-0vDKhlQCWh_VPlsG0R2q5xib0x41mV__________3tW8=DM-ArvK2cm5kGxS2CeckJB8IcF__________3ugzNCSG0xsw8Y150wMjZ_K5YBcMd-41lAPR20Ic7PskHT0CZxYF9401dx2SO4OAcHwWcvjBivuu4w-JBaIqc5KHsPlIJDgGY1EKcqOMfuHpgB10MNC7GR41ig1I00AvhaNG3CMF3ysnb4qG0ywmMxvU1DB__________m_J__________yFmW3VL7eK=VoOH3wa0bGAR0Mv3jmA9j4I1_W6O38gsjPh80RsoAw7L0QMdzGC4YBiKgY05fb6Th8hu4e-mnsOD1v-sFU_T1PaCe9eIBxERzmklanOMj9YT1TcR0p3Qa3KCb9ms5wU1cwYdAfO1GR41ig1I00Avh8hu4ispB6cK0SwtrRG-0jB__________m_J__________yFmW3VL7iI
115 ms
e_02a96280.jpg
384 ms
UBUpwK--MJI.jpg
391 ms
P9kCUlwdt5o.jpg
409 ms
e_584e969e.jpg
383 ms
YAHsPyog4Jw.jpg
392 ms
_Q-pZuk_FHw.jpg
386 ms
Wq4vDl_NP3k.jpg
384 ms
camera_50.png
129 ms
w_logo.png
172 ms
64hex.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
Form elements do not have associated labels
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
64hex.ru best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
64hex.ru SEO score
RU
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 64hex.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 64hex.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.
64hex.ru
Open Graph description is not detected on the main page of 64 Hex. 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: