6.2 sec in total
848 ms
4.9 sec
381 ms
Welcome to neo.co.jp homepage info - get ready to check Neo best content for Japan right away, or after learning these important things about neo.co.jp
ネオジャパンは、当社が持つ優れたIT技術と創造性でビジネスコミュニケーションツールを開発・提供し、より良い社会形成に貢献しています。
Visit neo.co.jpWe analyzed Neo.co.jp page load time and found that the first response time was 848 ms and then it took 5.3 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.co.jp performance score
name
value
score
weighting
Value9.2 s
0/100
10%
Value13.5 s
0/100
25%
Value12.7 s
3/100
10%
Value210 ms
88/100
30%
Value0.001
100/100
15%
Value14.4 s
9/100
10%
848 ms
786 ms
822 ms
501 ms
350 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 76% of them (69 requests) were addressed to the original Neo.co.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.7 sec) belongs to the original domain Neo.co.jp.
Page size can be reduced by 789.6 kB (19%)
4.1 MB
3.3 MB
In fact, the total size of Neo.co.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. 65% 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.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 19.4 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 93.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 93.0 kB or 41% of the original size.
Potential reduce by 72.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. Neo.co.jp needs all CSS files to be minified and compressed as it can save up to 72.1 kB or 85% of the original size.
Number of requests can be reduced by 32 (39%)
82
50
The browser has sent 82 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.co.jp
848 ms
common.css
786 ms
contents_module.css
822 ms
home.css
501 ms
home_animation.css
350 ms
xj.css
526 ms
jquery.js
1090 ms
common.js
737 ms
jquery.easing.1.3.js
835 ms
top.js
877 ms
jquery.imgpreload.min.js
912 ms
XjStorageLoaderirNews.js
941 ms
notosansjapanese.css
74 ms
analytics.js
88 ms
cse.js
87 ms
GetList.aspx
647 ms
hdr_logo.png
171 ms
blank.gif
179 ms
parts_spr.png
176 ms
p_top-01.jpg
1419 ms
p_top-01_sp.jpg
1396 ms
p_top-02.jpg
1441 ms
p_top-02_sp.jpg
994 ms
p_top-03.jpg
2169 ms
p_top-03_sp.jpg
1619 ms
p_top-04.jpg
1934 ms
p_top-04_sp.jpg
1920 ms
bn_pc_01.png
1576 ms
bn_pc_02.png
1759 ms
bn_sp.png
1732 ms
caption1.png
1795 ms
caption2.png
1890 ms
kamome.png
1920 ms
home_bnr_no1.png
2321 ms
home_p02.jpg
2203 ms
home_p03.jpg
2094 ms
home_p04.png
2238 ms
home_p05.jpg
2089 ms
home_p06.jpg
2246 ms
home_p07.jpg
2268 ms
news_icon05.png
2332 ms
news_icon_ir05.png
2359 ms
btn_rss.png
2398 ms
ftr_pagetop.png
2402 ms
ajax-loader.gif
2441 ms
bn_pc_02.png
2671 ms
icon1.png
2498 ms
icon2.png
2516 ms
icon3.png
2557 ms
icon4.png
2557 ms
icon5.png
2614 ms
NotoSansJP-Light.woff
189 ms
NotoSansJP-Thin.woff
248 ms
NotoSansJP-DemiLight.woff
357 ms
NotoSansJP-Regular.woff
420 ms
NotoSansJP-Medium.woff
419 ms
NotoSansJP-Bold.woff
421 ms
NotoSansJP-Black.woff
418 ms
icon6.png
2663 ms
collect
11 ms
jsapi
19 ms
default+ja.css
4 ms
default.css
34 ms
default+ja.I.js
13 ms
default.css
85 ms
async-ads.js
49 ms
google_custom_search_watermark.gif
20 ms
small-logo.png
26 ms
icon7.png
2506 ms
icon8.png
2548 ms
icon9.png
2542 ms
search_box_icon.png
45 ms
GetList.aspx
760 ms
icon10.png
1800 ms
icon11.png
1441 ms
icon12.png
1434 ms
icon13.png
1393 ms
icon14.png
1299 ms
icon15.png
1263 ms
icon16.png
1235 ms
icon17.png
1232 ms
icon18.png
1208 ms
icon19.png
1138 ms
icon20.png
1113 ms
icon21.png
1121 ms
icon22.png
1210 ms
icon23.png
1057 ms
icon24.png
1075 ms
icon25.png
1035 ms
icon26.png
985 ms
news_icon_ir01.png
962 ms
neo.co.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.co.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.co.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.co.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.co.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.co.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: