14.4 sec in total
4.1 sec
9.4 sec
865 ms
Visit anizines.com now to see the best up-to-date Anizines content for Japan and also check out these interesting facts you probably never knew about anizines.com
アニメ系を中心としたまとめブログの最終形『あにZねす』
Visit anizines.comWe analyzed Anizines.com page load time and found that the first response time was 4.1 sec and then it took 10.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
anizines.com performance score
name
value
score
weighting
Value5.5 s
6/100
10%
Value9.6 s
0/100
25%
Value15.9 s
0/100
10%
Value2,040 ms
7/100
30%
Value0.066
97/100
15%
Value17.0 s
4/100
10%
4119 ms
350 ms
572 ms
385 ms
385 ms
Our browser made a total of 128 requests to load all elements on the main page. We found that 45% of them (58 requests) were addressed to the original Anizines.com, 16% (21 requests) were made to Pbs.twimg.com and 4% (5 requests) were made to Tpc.googlesyndication.com. The less responsive or slowest element that took the longest time to load (4.1 sec) belongs to the original domain Anizines.com.
Page size can be reduced by 336.5 kB (13%)
2.5 MB
2.2 MB
In fact, the total size of Anizines.com main page is 2.5 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. 70% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 89.4 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 89.4 kB or 82% of the original size.
Potential reduce by 67.5 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. Anizines images are well optimized though.
Potential reduce by 61.2 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 61.2 kB or 37% of the original size.
Potential reduce by 118.4 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. Anizines.com needs all CSS files to be minified and compressed as it can save up to 118.4 kB or 82% of the original size.
Number of requests can be reduced by 50 (40%)
126
76
The browser has sent 126 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Anizines. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 15 to 1 for CSS and as a result speed up the page load time.
www.anizines.com
4119 ms
style.css
350 ms
style.css
572 ms
wpp.css
385 ms
styles.css
385 ms
style.css
393 ms
screen.css
520 ms
jquery.fancybox-1.3.7.min.css
567 ms
jetpack.css
804 ms
jquery.min.js
61 ms
loader.js
166 ms
vertical-m.css
571 ms
style.css
587 ms
adsbygoogle.js
5 ms
jquery.form.min.js
490 ms
scripts.js
384 ms
front.js
384 ms
jquery.optimum-lazy-load.min.js
389 ms
devicepx-jetpack.js
58 ms
gprofiles.js
58 ms
wpgroho.js
411 ms
jquery.fancybox-1.3.7.min.js
766 ms
jquery.easing.pack.js
571 ms
jquery.mousewheel.min.js
578 ms
e-201609.js
5 ms
base.js
607 ms
style.css
429 ms
wp-emoji-release.min.js
396 ms
favicon.st-hatena.com
591 ms
favicon.st-hatena.com
592 ms
favicon.st-hatena.com
595 ms
favicon.st-hatena.com
597 ms
favicon.st-hatena.com
621 ms
header2.jpg
1722 ms
miniemimusic120%C3%97175.png
573 ms
miniemipen120%C3%97175.png
520 ms
miniemiTVanime150%C3%97175.png
567 ms
search.png
328 ms
orange-large.png
480 ms
feedly-follow-rectangle-volume-big_2x.png
561 ms
img_05-100x100.jpg
869 ms
konjikinogashu-100x100.jpg
869 ms
dgrayman-100x100.jpg
757 ms
yakitatejapan-100x100.jpg
943 ms
nisemonogatari-100x100.jpg
762 ms
P1010267-100x100.jpg
954 ms
fairytail-100x100.jpg
1137 ms
boruto-100x100.jpg
1236 ms
BLACKLAGOON-100x100.jpg
1200 ms
doublea-tsu-100x100.jpg
1315 ms
kankoreanimeLogo.png
2129 ms
lovekanojyo.jpg
1746 ms
FLOWERKNIGHTGIRL.jpg
1718 ms
rss.png
1426 ms
utawarerumono2ki18wa43-380x200.jpg
1935 ms
gochiusa2ki1waED-380x200.jpg
1999 ms
utawarerumono2ki17wa38-380x200.jpg
2285 ms
utawarerumono2ki16wa19-380x200.jpg
2062 ms
utawarerumono2ki15wa32-380x200.jpg
2316 ms
kyokaraoreha-1-100x100.jpg
2071 ms
karanokyokai-100x100.jpg
2379 ms
ca-pub-6679897345182545.js
174 ms
zrt_lookup.html
168 ms
show_ads_impl.js
169 ms
miniemikanmusu.png
2294 ms
an_kana.gif
2145 ms
miniemiannai.png
2403 ms
ajs.php
385 ms
icomoon.woff
2483 ms
ads
308 ms
osd.js
20 ms
ads
313 ms
5171746271700867932
41 ms
abg.js
43 ms
m_js_controller.js
62 ms
googlelogo_color_112x36dp.png
111 ms
adstir.js
853 ms
lg.php
187 ms
13803484824688849145
35 ms
s
49 ms
x_button_blue2.png
46 ms
7-1I540iwtLQZRDhQUP9L-vt70m6ZeYTcveWqB03r34.js
5 ms
ad
385 ms
mnfuto401_60.gif
363 ms
82378670b189e795731381197406332e-2.jpg
977 ms
36ba252d.jpg
854 ms
cH9d0sC.jpg
63 ms
rzXgHpbs-1-1.jpg
1384 ms
4-1.jpg
54 ms
Pca4maSs.jpg
55 ms
miniemikeyholder.png
846 ms
miniemifut.png
847 ms
ajs.php
370 ms
ad
246 ms
lg.php
180 ms
widgets.js
166 ms
utawarerumono2ki18wa43-600x400.jpg
870 ms
miniemib.png
405 ms
g.gif
104 ms
25b6.png
62 ms
hovercard.css
36 ms
services.css
133 ms
timeline.1b43d11859b7663a2225b885f87704a5.js
131 ms
syndication
96 ms
524064239808294912
194 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
31 ms
timeline.4d087f49a21e27038d9769d7c976b8fa.default.css
114 ms
UycM_Xp7_normal.jpeg
86 ms
AUQg33lI_normal.jpg
79 ms
CbDqc25UYAAfsLb.jpg
84 ms
CalpVZ0VIAECL2Z.jpg
83 ms
CZueGXYUkAAmOX1.jpg
80 ms
CZAfkWKWYAAISLl.jpg
81 ms
CYhZp5dUoAA0OnH.jpg
85 ms
CX9mpUpUQAAc0Up.jpg
88 ms
CXZWJOBUkAArYVT.jpg
88 ms
CXOCPOyUQAEfW7T.jpg
85 ms
CXFZBPMUQAA5sbR.jpg
84 ms
CXAm5Y5UEAA2mQD.jpg
86 ms
CW0zp3nUkAABOJf.jpg
94 ms
CWRmC1OVAAA94X7.jpg
93 ms
CV9OWWFUAAQfxxV.jpg
94 ms
CVytqzEUsAA-B8v.jpg
93 ms
CVtkirjUwAE_sZt.jpg
98 ms
CVoUrdPUkAABCfv.jpg
93 ms
CViF4e2UwAAzr3r.jpg
95 ms
CVciaoMUkAAWnI6.jpg:large
96 ms
CVZxWQuUAAEjoj8.jpg
93 ms
anizines.com accessibility score
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-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
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
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
anizines.com 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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
anizines.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Anizines.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Anizines.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.
anizines.com
Open Graph description is not detected on the main page of Anizines. 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: