7.1 sec in total
994 ms
5.8 sec
309 ms
Welcome to neo.jp homepage info - get ready to check Neo best content for Japan right away, or after learning these important things about neo.jp
ネオジャパンの企業ウェブサイト。グループウェア「desknet's NEO」を始めとしたビジネスICTツールを開発・提供し、豊かな社会形成に貢献しています。
Visit neo.jpWe analyzed Neo.jp page load time and found that the first response time was 994 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
neo.jp performance score
name
value
score
weighting
Value9.2 s
0/100
10%
Value15.6 s
0/100
25%
Value11.8 s
4/100
10%
Value130 ms
96/100
30%
Value0.01
100/100
15%
Value13.9 s
10/100
10%
994 ms
755 ms
818 ms
493 ms
340 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 76% of them (71 requests) were addressed to the original Neo.jp, 8% (7 requests) were made to Fonts.gstatic.com and 8% (7 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Neo.jp.
Page size can be reduced by 819.5 kB (20%)
4.1 MB
3.3 MB
In fact, the total size of Neo.jp main page is 4.1 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 3.7 MB which makes up the majority of the site volume.
Potential reduce by 19.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 19.5 kB or 73% of the original size.
Potential reduce by 605.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. Obviously, Neo needs image optimization as it can save up to 605.1 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 125.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 125.1 kB or 53% of the original size.
Potential reduce by 69.9 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. Neo.jp needs all CSS files to be minified and compressed as it can save up to 69.9 kB or 84% of the original size.
Number of requests can be reduced by 34 (40%)
84
50
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Neo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 13 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
neo.jp
994 ms
common.css
755 ms
contents_module.css
818 ms
home.css
493 ms
home_animation.css
340 ms
xj.css
533 ms
jquery.js
1533 ms
common.js
570 ms
jquery.easing.1.3.js
818 ms
top.js
885 ms
jquery.imgpreload.min.js
774 ms
XjStorageLoaderirNews.js
901 ms
notosansjapanese.css
57 ms
analytics.js
96 ms
cse.js
96 ms
GetList.aspx
733 ms
hdr_logo.png
200 ms
blank.gif
176 ms
parts_spr.png
167 ms
p_top-01.jpg
1798 ms
p_top-01_sp.jpg
1599 ms
p_top-02.jpg
1967 ms
p_top-02_sp.jpg
1678 ms
p_top-03.jpg
1366 ms
p_top-03_sp.jpg
1932 ms
p_top-04.jpg
2221 ms
p_top-04_sp.jpg
2310 ms
bn_pc_01.png
1829 ms
bn_pc_02.png
2123 ms
bn_sp.png
1979 ms
caption1.png
2125 ms
caption2.png
2129 ms
kamome.png
2130 ms
home_bnr_no1.png
2450 ms
home_p02.jpg
2702 ms
home_p03.jpg
2294 ms
home_p04.png
2431 ms
home_p05.jpg
2394 ms
home_p06.jpg
2457 ms
home_p07.jpg
2487 ms
news_icon05.png
2561 ms
news_icon_ir05.png
2581 ms
news_icon01.png
2613 ms
btn_rss.png
2620 ms
ftr_pagetop.png
2663 ms
ajax-loader.gif
2732 ms
bn_pc_02.png
2883 ms
icon1.png
2776 ms
icon2.png
2784 ms
icon3.png
2840 ms
icon4.png
2893 ms
NotoSansJP-Light.woff
53 ms
NotoSansJP-Thin.woff
210 ms
NotoSansJP-DemiLight.woff
251 ms
NotoSansJP-Regular.woff
250 ms
NotoSansJP-Medium.woff
249 ms
NotoSansJP-Bold.woff
251 ms
NotoSansJP-Black.woff
252 ms
icon5.png
2899 ms
collect
14 ms
jsapi
18 ms
default+ja.css
4 ms
default.css
28 ms
default+ja.I.js
10 ms
default.css
117 ms
async-ads.js
116 ms
google_custom_search_watermark.gif
80 ms
small-logo.png
25 ms
search_box_icon.png
24 ms
icon6.png
2778 ms
icon7.png
2778 ms
icon8.png
2825 ms
GetList.aspx
730 ms
icon9.png
1669 ms
icon10.png
1492 ms
icon11.png
1400 ms
icon12.png
1310 ms
icon13.png
1287 ms
icon14.png
1266 ms
icon15.png
1223 ms
icon16.png
1267 ms
icon17.png
1159 ms
icon18.png
1144 ms
icon19.png
1150 ms
icon20.png
1208 ms
icon21.png
1156 ms
icon22.png
1124 ms
icon23.png
1125 ms
icon24.png
1049 ms
icon25.png
1044 ms
icon26.png
1040 ms
news_icon_ir02.png
1095 ms
news_icon_ir01.png
1101 ms
neo.jp 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.
neo.jp 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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
neo.jp 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
JA
JA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Neo.jp 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 Neo.jp 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.
neo.jp
Open Graph description is not detected on the main page of Neo. 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: