6 sec in total
434 ms
5 sec
617 ms
Visit notteco.jp now to see the best up-to-date Notteco content for Japan and also check out these interesting facts you probably never knew about notteco.jp
日本最大級の長距離ライドシェア(相乗り)サービス、notteco(のってこ!)。空席を持て余しているドライバーと同じ方面に安く移動したい同乗者をマッチング。移動にかかる実費をみんなで割勘するので、とっても経済的。
Visit notteco.jpWe analyzed Notteco.jp page load time and found that the first response time was 434 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
notteco.jp performance score
name
value
score
weighting
Value17.0 s
0/100
10%
Value25.2 s
0/100
25%
Value21.1 s
0/100
10%
Value1,040 ms
26/100
30%
Value0
100/100
15%
Value27.2 s
1/100
10%
434 ms
151 ms
306 ms
462 ms
296 ms
Our browser made a total of 87 requests to load all elements on the main page. We found that 76% of them (66 requests) were addressed to the original Notteco.jp, 6% (5 requests) were made to Maps.googleapis.com and 2% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (3.8 sec) relates to the external source Query.yahooapis.com.
Page size can be reduced by 863.2 kB (19%)
4.5 MB
3.6 MB
In fact, the total size of Notteco.jp main page is 4.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. 60% of websites need less resources to load. Images take 3.4 MB which makes up the majority of the site volume.
Potential reduce by 35.3 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. This page needs HTML code to be minified as it can gain 5.8 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 35.3 kB or 79% of the original size.
Potential reduce by 107.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. Notteco images are well optimized though.
Potential reduce by 540.9 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 540.9 kB or 68% of the original size.
Potential reduce by 179.7 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. Notteco.jp needs all CSS files to be minified and compressed as it can save up to 179.7 kB or 85% of the original size.
Number of requests can be reduced by 42 (51%)
83
41
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Notteco. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
notteco.jp
434 ms
jquery-ui.css
151 ms
jcf.css
306 ms
style.css
462 ms
style-add.css
296 ms
jquery-1.10.2.min.js
460 ms
jquery-ui.min.js
448 ms
jcf.js
306 ms
jcf.select.js
442 ms
main.js
450 ms
jquery.bxslider.css
454 ms
css
59 ms
jquery.carouselcycle.js
594 ms
js
81 ms
search.js
613 ms
jquery.cookie.js
614 ms
community.js
614 ms
swiper.min.js
616 ms
videoLightning.min.js
614 ms
jquery.easing.1.3.js
739 ms
jquery.bxslider.min.js
742 ms
jquery.xdomainajax.js
740 ms
login_form.js
753 ms
sns.js
751 ms
yql
3779 ms
fbevents.js
109 ms
main-1.jpg
1039 ms
main-2.jpg
878 ms
main-3.jpg
1184 ms
main-4.jpg
1171 ms
man.png
163 ms
wallet.png
163 ms
license.png
322 ms
step-1.png
325 ms
step-2.png
455 ms
step-3.png
474 ms
ski_478_178.png
1039 ms
charmant_pc.png
1224 ms
koide_pc.png
1171 ms
yutty_pc.png
1188 ms
tabica_pc.jpg
1186 ms
request-pc.jpg
1610 ms
pc-driver-1.jpg
1466 ms
pc-driver-2.jpg
1331 ms
pc-driver-3.jpg
1480 ms
facebook.png
1335 ms
twitter.png
1374 ms
gtm.js
107 ms
logo.png
1481 ms
1485 ms
common.js
33 ms
util.js
67 ms
controls.js
84 ms
places_impl.js
81 ms
all.js
79 ms
pin-1.png
1421 ms
pin-2.png
1508 ms
search.png
1521 ms
car-1.png
1526 ms
kisei-1.png
1872 ms
kankou-1.png
1750 ms
kansen-1.png
1654 ms
activity-1.png
1802 ms
hobby-1.png
1813 ms
volunteer-1.png
1823 ms
user-1.png
1801 ms
quo-left.png
1898 ms
quo-right.png
1948 ms
zhcz-_WihjSQC0oHJ9TCYC3USBnSvpkopQaUR-2r7iU.ttf
142 ms
204 ms
analytics.js
57 ms
user-2.png
1895 ms
powered-by-google-on-white3.png
128 ms
user-3.png
1890 ms
autocomplete-icons.png
144 ms
collect
17 ms
collect
113 ms
182 ms
xd_arbiter.php
94 ms
xd_arbiter.php
159 ms
user-4.png
1758 ms
ga-audiences
31 ms
car-2.png
1807 ms
media-1.png
1699 ms
bx_loader.gif
1788 ms
left.png
1329 ms
right.png
1178 ms
notteco.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
notteco.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
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
notteco.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
Tap targets are not sized appropriately
JA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Notteco.jp can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Notteco.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.
notteco.jp
Open Graph description is not detected on the main page of Notteco. 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: