4.6 sec in total
243 ms
3.8 sec
582 ms
Visit say-hi.me now to see the best up-to-date Say Hi content for Russia and also check out these interesting facts you probably never knew about say-hi.me
Сей-Хай - это онлайн издание про веб-дизайн, ux дизайн, моушн дизайн, графический дизайн, каллиграфию, рисование, живопись. Полезные советы, уроки и гайды.
Visit say-hi.meWe analyzed Say-hi.me page load time and found that the first response time was 243 ms and then it took 4.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
say-hi.me performance score
name
value
score
weighting
Value4.2 s
20/100
10%
Value10.3 s
0/100
25%
Value17.4 s
0/100
10%
Value11,150 ms
0/100
30%
Value0.418
23/100
15%
Value33.2 s
0/100
10%
243 ms
546 ms
97 ms
112 ms
118 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 80% of them (95 requests) were addressed to the original Say-hi.me, 3% (3 requests) were made to Fonts.googleapis.com and 3% (3 requests) were made to Static.addtoany.com. The less responsive or slowest element that took the longest time to load (955 ms) relates to the external source Mc.yandex.ru.
Page size can be reduced by 265.8 kB (20%)
1.3 MB
1.1 MB
In fact, the total size of Say-hi.me main page is 1.3 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. 65% of websites need less resources to load. Images take 673.0 kB which makes up the majority of the site volume.
Potential reduce by 213.5 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 213.5 kB or 87% of the original size.
Potential reduce by 12.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. Say Hi images are well optimized though.
Potential reduce by 19.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. This website has mostly compressed JavaScripts.
Potential reduce by 20.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. Say-hi.me needs all CSS files to be minified and compressed as it can save up to 20.7 kB or 30% of the original size.
Number of requests can be reduced by 46 (41%)
113
67
The browser has sent 113 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Say Hi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
say-hi.me
243 ms
say-hi.me
546 ms
css
97 ms
css
112 ms
style.css
118 ms
responsive.css
230 ms
font-awesome.min.css
310 ms
prettyPhoto.css
315 ms
sk-style.css
314 ms
style.min.css
321 ms
styles.css
323 ms
symple_shortcodes_styles.css
412 ms
polls-css.css
417 ms
postratings-css.css
417 ms
wpp.css
420 ms
style.css
424 ms
addtoany.min.css
426 ms
colorbox.min.css
434 ms
page.js
80 ms
jquery.min.js
75 ms
addtoany.min.js
522 ms
wpp.min.js
515 ms
adsbygoogle.js
214 ms
jquery.prettyPhoto.js
617 ms
h0y8i8.js
120 ms
bunyad-theme.js
695 ms
jquery.flexslider-min.js
696 ms
jquery.sticky-sidebar.min.js
628 ms
gravitate_event_tracking.js
692 ms
wp-polyfill.min.js
798 ms
index.js
695 ms
polls-js.js
797 ms
postratings-js.js
800 ms
postviews-cache.js
798 ms
frontend.min.js
800 ms
jquery.colorbox.1.5.9-min.js
801 ms
wp-embed.min.js
861 ms
OneSignalSDK.js
72 ms
css
22 ms
wp-emoji-release.min.js
480 ms
fbevents.js
187 ms
ga-54e51056211dda674100cc5b323a58ad.js
505 ms
Say-hi-main-logo.png
256 ms
8f1c919795f77ea_600x460_left.jpg
402 ms
021f36988ee6210_474x240_left.jpg
408 ms
1d1acbb84d3e345_235x215_left.jpg
346 ms
f906235653e9030_235x215_left.png
399 ms
5b9bebc3166fcce_326x205_left.jpg
402 ms
5f9476a81eb267e_163x102_left.jpg
464 ms
7d9f62f1e5488d8_163x102_left.jpg
500 ms
bf2b247a079fdac_163x102_left.jpg
501 ms
02a8ce15dac6559_163x102_left.jpg
500 ms
faa0e004413d44b_336x200_left.jpg
501 ms
c45e77061b2a481_336x200_left.jpg
502 ms
0d42796af582129_104x69_left.jpg
591 ms
d6cf7db09aac605_104x69_left.jpg
588 ms
e17d3cfd2450202_104x69_left.jpg
589 ms
63286e7abd272ec_104x69_left.png
589 ms
8455858466135a8_104x69_left.jpg
587 ms
d8eabd7f83319ad_104x69_left.png
590 ms
021f36988ee6210_336x200_left.jpg
773 ms
481ec53c5739540_336x200_left.jpg
778 ms
75afbba717df95f_104x69_left.jpg
775 ms
sdk.js
76 ms
098a81981128c26_104x69_left.jpg
773 ms
hit
587 ms
8a654487eb74936_104x69_left.jpg
702 ms
8a60e04ebdfa7e2_104x69_left.jpg
700 ms
f79d941d88273fa_104x69_left.png
746 ms
6a51f2d79f943b8_104x69_left.jpg
764 ms
397dc76dda2ea5d_336x200_left.jpg
676 ms
86a05b4ff1c3f64_336x200_left.jpg
682 ms
6b0c384e152b61d_104x69_left.jpg
687 ms
bee31452c2ee94e_104x69_left.jpg
689 ms
29bfe8308fd21d8_104x69_left.jpg
753 ms
f8e31b727d94c0d_104x69_left.jpg
760 ms
sdk.js
10 ms
e4e5a9cec67ff13_104x69_left.jpg
714 ms
560a59371c3b460_104x69_left.jpg
720 ms
01c174967795c75_336x200_left.jpg
727 ms
font
90 ms
font
144 ms
fontawesome-webfont.woff
832 ms
font
146 ms
96 ms
f87735258c9d732_336x200_left.jpg
693 ms
4e6d0a104276c58_336x200_left.jpg
659 ms
f5ead7b48709596_336x200_left.jpg
669 ms
8f90b470d34e807_336x200_left.jpg
675 ms
ea28f52a794a07b_336x200_left.jpg
706 ms
9f38aac44a3d6ce_312x198_left.jpg
686 ms
collect
107 ms
2eb0deeab7e6bda_312x198_left.jpg
667 ms
2eacc1bca2af966_312x198_left.jpg
675 ms
f3a08f0aebe63dc_312x198_left.jpg
682 ms
1d1acbb84d3e345_336x200_left.jpg
702 ms
c2b9c7f1ae2dd72_336x200_left.jpg
696 ms
6186f82fa7e575d_336x200_left.jpg
747 ms
tag.js
955 ms
wp-polyfill-fetch.min.js
684 ms
wp-polyfill-dom-rect.min.js
687 ms
wp-polyfill-url.min.js
704 ms
wp-polyfill-formdata.min.js
722 ms
8d4c4db4feb652e_336x200_left.jpg
871 ms
1c5516cf2ad926e_336x200_left.jpg
874 ms
js
59 ms
hit
171 ms
007314c8dff0996_326x205_left.png
697 ms
557aa6718383b9a_163x102_left.jpg
697 ms
99ee6af445403a0_163x102_left.jpg
694 ms
a4d2933b733c114_163x102_left.jpg
693 ms
37a16c8b1d4127e_163x102_left.jpg
693 ms
Say-hi-main-logo_white.png
834 ms
admin-ajax.php
657 ms
sm.25.html
141 ms
eso.D0Uc7kY6.js
285 ms
rating_over.png
272 ms
advert.gif
621 ms
sync_cookie_image_decide
134 ms
say-hi.me 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
say-hi.me 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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
say-hi.me 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
![]()
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Say-hi.me can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it does not match the claimed English language. Our system also found out that Say-hi.me 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.
say-hi.me
Open Graph data is detected on the main page of Say Hi. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: