2.7 sec in total
12 ms
1.5 sec
1.2 sec
Welcome to neleus.wordpress.com homepage info - get ready to check Neleus Wordpress best content for United States right away, or after learning these important things about neleus.wordpress.com
飼育中の魚と水草、増えていくインテリアについて解説する
Visit neleus.wordpress.comWe analyzed Neleus.wordpress.com page load time and found that the first response time was 12 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
neleus.wordpress.com performance score
name
value
score
weighting
Value2.8 s
56/100
10%
Value3.9 s
53/100
25%
Value4.6 s
70/100
10%
Value980 ms
28/100
30%
Value0
100/100
15%
Value15.0 s
8/100
10%
12 ms
442 ms
107 ms
113 ms
120 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Neleus.wordpress.com, 35% (28 requests) were made to S2.wp.com and 25% (20 requests) were made to Neleus.files.wordpress.com. The less responsive or slowest element that took the longest time to load (839 ms) relates to the external source Neleus.files.wordpress.com.
Page size can be reduced by 464.8 kB (23%)
2.0 MB
1.6 MB
In fact, the total size of Neleus.wordpress.com main page is 2.0 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. 50% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 57.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 57.5 kB or 73% of the original size.
Potential reduce by 239 B
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. Neleus Wordpress images are well optimized though.
Potential reduce by 375.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 375.0 kB or 75% of the original size.
Potential reduce by 32.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. Neleus.wordpress.com needs all CSS files to be minified and compressed as it can save up to 32.1 kB or 73% of the original size.
Number of requests can be reduced by 43 (59%)
73
30
The browser has sent 73 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Neleus 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 10 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
neleus.wordpress.com
12 ms
neleus.wordpress.com
442 ms
107 ms
global.css
113 ms
120 ms
style.css
111 ms
gprofiles.js
241 ms
wpgroho.js
104 ms
112 ms
jetpack-carousel.css
112 ms
tiled-gallery.css
116 ms
117 ms
widgets.js
430 ms
114 ms
725X1342.skimlinks.js
181 ms
w.js
117 ms
merriweather.css
16 ms
bkg-body.jpg
34 ms
img_1687.jpg
444 ms
IMG_1612.JPG
437 ms
aquarium100_33.gif
438 ms
480144f5ddc2d34c8255cfb8e2b0c56a
468 ms
banner_22.gif
483 ms
aquarium88_31.gif
747 ms
img_1690.jpg
427 ms
img_1594.jpg
425 ms
img_1591.jpg
426 ms
img_0533.jpg
464 ms
img_0526.jpg
425 ms
img_0539.jpg
586 ms
img_0561.jpg
592 ms
img_0564.jpg
576 ms
sdim0134.jpg
579 ms
sdim0138.jpg
602 ms
sdim0146.jpg
596 ms
sdim0148.jpg
705 ms
sdim0154.jpg
694 ms
sdim0156.jpg
708 ms
sdim0165.jpg
706 ms
sdim0115.jpg
714 ms
sdim0123.jpg
728 ms
sdim0125.jpg
814 ms
sdim0129.jpg
839 ms
header-bkg.png
179 ms
logo-icon.png
179 ms
rss-ico.png
178 ms
menu-left-h.png
178 ms
menu-right-h.png
177 ms
menu-left.png
244 ms
menu-right.png
243 ms
sl-t.png
243 ms
post-head.png
244 ms
p-cat-ico.png
243 ms
p-com-ico.png
242 ms
p-con-li.png
403 ms
p-tag.png
403 ms
sl-b.png
402 ms
sr-t.png
401 ms
widget-top.png
401 ms
widget-bottom.png
402 ms
sr-h3-ico.png
411 ms
categ-arrow.png
410 ms
categ-bottom.png
411 ms
sr-b.png
411 ms
9a115ed36ac718b4e2377b31e24c5c33
236 ms
global-print.css
173 ms
Noticons.svg
226 ms
BaABdRAi2AAAA
1 ms
merriweather-bold-webfont.ttf
64 ms
merriweather-regular-webfont.ttf
215 ms
merriweather-light-webfont.ttf
214 ms
px.gif
263 ms
257 ms
hovercard.css
97 ms
services.css
96 ms
px.gif
136 ms
g.gif
133 ms
g.gif
132 ms
g.gif
131 ms
neleus.wordpress.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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
neleus.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
Issues were logged in the Issues panel in Chrome Devtools
neleus.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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Neleus.wordpress.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 Neleus.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.
neleus.wordpress.com
Open Graph data is detected on the main page of Neleus Wordpress. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: