6.6 sec in total
100 ms
5.9 sec
519 ms
Visit hanizu.wordpress.com now to see the best up-to-date Hanizu Wordpress content for United States and also check out these interesting facts you probably never knew about hanizu.wordpress.com
אני רוצה עולם טוב יותר, אך הכלים שרכשתי הם בעיקר ביקורתיים - יש לי תשובות, אך יותר ביקורת, וזו לא תמיד בונה. לעיתים ביקורת היא רק ביקורת.
Visit hanizu.wordpress.comWe analyzed Hanizu.wordpress.com page load time and found that the first response time was 100 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.
hanizu.wordpress.com performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value3.9 s
53/100
25%
Value10.5 s
7/100
10%
Value2,680 ms
4/100
30%
Value0
100/100
15%
Value21.4 s
1/100
10%
100 ms
573 ms
267 ms
278 ms
223 ms
Our browser made a total of 152 requests to load all elements on the main page. We found that 2% of them (3 requests) were addressed to the original Hanizu.wordpress.com, 12% (18 requests) were made to Apis.google.com and 9% (13 requests) were made to Polldaddy.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Connect.facebook.net.
Page size can be reduced by 687.3 kB (73%)
945.6 kB
258.3 kB
In fact, the total size of Hanizu.wordpress.com main page is 945.6 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. 65% of websites need less resources to load. HTML takes 439.2 kB which makes up the majority of the site volume.
Potential reduce by 385.0 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 385.0 kB or 88% of the original size.
Potential reduce by 2.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. Hanizu Wordpress images are well optimized though.
Potential reduce by 270.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 270.1 kB or 70% of the original size.
Potential reduce by 30.1 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. Hanizu.wordpress.com needs all CSS files to be minified and compressed as it can save up to 30.1 kB or 82% of the original size.
Number of requests can be reduced by 87 (60%)
144
57
The browser has sent 144 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hanizu Wordpress. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 73 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
hanizu.wordpress.com
100 ms
hanizu.wordpress.com
573 ms
267 ms
278 ms
style-rtl.css
223 ms
rtl.css
223 ms
gprofiles.js
321 ms
wpgroho.js
233 ms
260 ms
rating.js
550 ms
share.js
312 ms
widgets.js
364 ms
style.css
265 ms
253 ms
w.js
271 ms
merriweather.css
193 ms
8a42b2cea2a8c564a26550c6f5188516
707 ms
pinit_fg_en_rect_gray_20.png
669 ms
8f16ff5edab13184bd7936838437b826
703 ms
7d6fe40e7b31703659e129e1753704ad
661 ms
red-medium.png
353 ms
loading.gif
352 ms
8d59cac395d8f95cf6325eee74a4801c
1022 ms
share_2.png
307 ms
button1.html
615 ms
Genericons.svg
303 ms
8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=
8 ms
button1.html
607 ms
button1.html
629 ms
button1.html
588 ms
button1.html
619 ms
button1.html
609 ms
button1.html
690 ms
button1.html
736 ms
button1.html
681 ms
button1.html
770 ms
sdk.js
1870 ms
rate.php
326 ms
rate.php
483 ms
rate.php
713 ms
rate.php
639 ms
rate.php
639 ms
rate.php
638 ms
rate.php
637 ms
rate.php
693 ms
rate.php
848 ms
rate.php
849 ms
pinit.js
489 ms
widgets.js
285 ms
plusone.js
544 ms
Noticons.svg
112 ms
BaABdRAi2AAAA
106 ms
merriweather-bold-webfont.ttf
111 ms
merriweather-regular-webfont.ttf
416 ms
merriweather-light-webfont.ttf
455 ms
hovercard.css
227 ms
services.css
385 ms
in.js
553 ms
button.65b4bc8f0d6592fdc51d322b3f197660.js
193 ms
g.gif
343 ms
g.gif
445 ms
g.gif
515 ms
button-embed.js
168 ms
follow_button.64a917b4a230f163048902c783e1530f.he.html
264 ms
tweet_button.64a917b4a230f163048902c783e1530f.he.html
490 ms
button_info.json
1233 ms
button_info.json
1354 ms
button_info.json
1352 ms
button_info.json
1353 ms
button_info.json
1351 ms
button_info.json
1350 ms
button_info.json
1525 ms
button_info.json
1565 ms
pinit_main.js
253 ms
button_info.json
1556 ms
cb=gapi.loaded_0
237 ms
cb=gapi.loaded_1
334 ms
fastbutton
532 ms
fastbutton
527 ms
fastbutton
525 ms
fastbutton
519 ms
fastbutton
517 ms
fastbutton
511 ms
fastbutton
1469 ms
fastbutton
1461 ms
fastbutton
1452 ms
fastbutton
1453 ms
button_info.json
1496 ms
star-yellow-sml.png
374 ms
info.png
375 ms
secureAnonymousFramework
271 ms
count.json
1329 ms
count.json
1264 ms
count.json
1263 ms
count.json
1316 ms
count.json
1328 ms
count.json
1328 ms
count.json
1404 ms
count.json
1411 ms
count.json
1442 ms
count.json
1432 ms
postmessageRelay
1254 ms
rs=AGLTcCPyaY-vig897Y3MEupcsFg63drNEQ
730 ms
share
1127 ms
sprite_connect_v14.png
1105 ms
share
1162 ms
share
1150 ms
share
1092 ms
share
1074 ms
share
983 ms
share
870 ms
share
816 ms
share
743 ms
share
764 ms
406 ms
cb=gapi.loaded_0
213 ms
cb=gapi.loaded_1
220 ms
grlryt2bdKIyfMSOhzd1eA.woff
320 ms
xd_arbiter.php
649 ms
3193398744-postmessagerelay.js
147 ms
rpc:shindig_random.js
84 ms
jot.html
85 ms
cb=gapi.loaded_0
26 ms
botd.gif
180 ms
share_button.php
92 ms
share_button.php
169 ms
share_button.php
197 ms
share_button.php
240 ms
share_button.php
240 ms
share_button.php
210 ms
share_button.php
238 ms
share_button.php
253 ms
share_button.php
291 ms
share_button.php
309 ms
page.php
366 ms
JzIxkC-0qHF.js
669 ms
LVx-xkvaJ0b.png
531 ms
NDAwyHE1HT_.css
298 ms
XCdv7aD40Gm.js
486 ms
OFhNVaVcYdk.js
508 ms
nw0sMxy_KfY.js
362 ms
1959989_649495585162418_5960710469250062948_n.jpg
402 ms
11903891_709724719139504_8256027108874927915_n.jpg
469 ms
10702106_10152689970074594_2038054760772181971_n.jpg
609 ms
231026_100280166729307_2483242_n.jpg
642 ms
11026165_1014255791935787_2257867514449576835_n.jpg
631 ms
wL6VQj7Ab77.png
133 ms
T4r822UJYBN.png
133 ms
R9GKCzjAnbk.js
71 ms
AWWjhOengNF.js
74 ms
YnSasnyq68i.js
74 ms
kQf_jlUv-kX.js
72 ms
hanizu.wordpress.com 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.
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 IDs are not unique
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
hanizu.wordpress.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
hanizu.wordpress.com SEO score
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
IW
HE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hanizu.wordpress.com can be misinterpreted by Google and other search engines. Our service has detected that Hebrew is used on the page, and it does not match the claimed language. Our system also found out that Hanizu.wordpress.com 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.
hanizu.wordpress.com
Open Graph data is detected on the main page of Hanizu Wordpress. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: