10.2 sec in total
1.5 sec
7.6 sec
1.1 sec
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 1.5 sec and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
neo.jp performance score
name
value
score
weighting
Value10.5 s
0/100
10%
Value14.9 s
0/100
25%
Value14.3 s
1/100
10%
Value760 ms
39/100
30%
Value0.757
6/100
15%
Value58.4 s
0/100
10%
1484 ms
474 ms
39 ms
76 ms
553 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Neo.jp, 1% (1 request) were made to Cmp.datasign.co and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.4 sec) relates to the external source Neo.co.jp.
Page size can be reduced by 2.3 MB (20%)
11.5 MB
9.1 MB
In fact, the total size of Neo.jp main page is 11.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. 40% of websites need less resources to load. Images take 9.0 MB which makes up the majority of the site volume.
Potential reduce by 100.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 100.5 kB or 86% of the original size.
Potential reduce by 588.2 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. Neo images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 65% of the original size.
Potential reduce by 508.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.jp needs all CSS files to be minified and compressed as it can save up to 508.1 kB or 85% of the original size.
Number of requests can be reduced by 79 (77%)
103
24
The browser has sent 103 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 14 to 1 for JavaScripts and from 54 to 1 for CSS and as a result speed up the page load time.
www.neo.co.jp
1484 ms
style.css
474 ms
cmp.js
39 ms
js
76 ms
nopro.css
553 ms
nopro.css
554 ms
nopro.css
555 ms
nopro.css
554 ms
nopro.css
625 ms
nopro.css
630 ms
nopro.css
650 ms
nopro.css
654 ms
style.min.css
1073 ms
style.css
565 ms
style.css
629 ms
style.css
633 ms
style.css
658 ms
style.css
663 ms
style.css
728 ms
style.css
785 ms
style.css
790 ms
style.css
818 ms
style.css
824 ms
style.css
1055 ms
style.css
940 ms
style.css
946 ms
style.css
979 ms
slick.css
986 ms
slick-theme.css
1097 ms
style.css
1103 ms
spider.css
1140 ms
style.css
1147 ms
style.css
1217 ms
style.css
1235 ms
style.css
1253 ms
style.css
1259 ms
style.css
1300 ms
blocks.css
1308 ms
CYCfEHkXb3kb2NAR.js
754 ms
styles.css
1074 ms
vk-components.css
1012 ms
swiper-bundle.min.css
1018 ms
bootstrap_vk_using.css
1182 ms
original-margin.css
1068 ms
flex-list.css
1077 ms
nj-custom-header.css
1080 ms
file-uploader.css
1102 ms
block-build.css
1391 ms
all.min.css
1614 ms
menu.css
1073 ms
page-top.css
1087 ms
product.css
1112 ms
product-simple.css
1080 ms
news.css
1140 ms
column-list.css
1151 ms
column.css
1110 ms
button.css
1123 ms
footer.css
1146 ms
all.min.js
2041 ms
spider.js
1101 ms
jquery-3.7.1.min.js
1261 ms
index.js
1102 ms
index.js
1140 ms
swiper-bundle.min.js
1301 ms
vk-slider.min.js
1222 ms
menu.js
1199 ms
headline.js
1194 ms
product.js
1225 ms
footer-menu.js
1269 ms
menu-logo-red.svg
193 ms
menu-logo-white.svg
208 ms
menu-lang-icon-red.svg
270 ms
menu-lang-icon-white.svg
280 ms
right-arrow-red.png
341 ms
menu-open-icon-red.svg
353 ms
menu-open-icon-white.svg
370 ms
menu-close-icon.svg
428 ms
left-arrow-red.png
437 ms
bottom-arrow-black.png
510 ms
top-arrow-black.png
514 ms
top-shortcut-1.png
532 ms
top-shortcut-1.png
585 ms
top-shortcut-2.png
596 ms
top-shortcut-2.png
677 ms
top-shortcut-3.png
675 ms
top-shortcut-3.png
694 ms
desknets-neo-mock.png
1057 ms
app-suite-mock.png
1383 ms
chat-luck-mock.png
784 ms
desknets-neo.png
837 ms
link-icon-white.svg
844 ms
app-suite.png
856 ms
chat-luck.png
948 ms
desknets-neo-mock.png
1645 ms
app-suite-mock.png
3366 ms
chat-luck-mock.png
1669 ms
column_20240423.png
1114 ms
column_20240416.jpg
1170 ms
column_20240328.jpg
1235 ms
right-arrow-white.png
1325 ms
NotoSansJP-Bold.ttf
1893 ms
NotoSansJP-Regular.ttf
2056 ms
facebook-icon.png
1421 ms
x-icon.png
1512 ms
triangle-white.svg
1614 ms
top-background.png
1790 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.
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
neo.jp best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Missing source maps for large first-party JavaScript
neo.jp 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
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: