12.1 sec in total
1.1 sec
10.8 sec
256 ms
Click here to check amazing Seasea content for Japan. Otherwise, check out these important facts you probably never knew about seasea.jp
ボート・中古ボート・マリンジェット・船外機をはじめとする製品全般から、レンタルボート・大阪、神戸での船舶免許の取得まで、お客様と海をつなぐためのトータルマリンサービスをご提供します。
Visit seasea.jpWe analyzed Seasea.jp page load time and found that the first response time was 1.1 sec and then it took 11 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
seasea.jp performance score
name
value
score
weighting
Value4.0 s
22/100
10%
Value12.8 s
0/100
25%
Value19.4 s
0/100
10%
Value530 ms
56/100
30%
Value1.002
2/100
15%
Value16.4 s
5/100
10%
1096 ms
347 ms
374 ms
391 ms
391 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 95% of them (82 requests) were addressed to the original Seasea.jp, 3% (3 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (6.7 sec) belongs to the original domain Seasea.jp.
Page size can be reduced by 128.9 kB (6%)
2.3 MB
2.1 MB
In fact, the total size of Seasea.jp main page is 2.3 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. 25% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 22.0 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.3 kB, which is 18% 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 22.0 kB or 77% of the original size.
Potential reduce by 26.5 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. Seasea images are well optimized though.
Potential reduce by 48.4 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 48.4 kB or 61% of the original size.
Potential reduce by 31.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. Seasea.jp needs all CSS files to be minified and compressed as it can save up to 31.9 kB or 83% of the original size.
Number of requests can be reduced by 26 (31%)
84
58
The browser has sent 84 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Seasea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
seasea.jp
1096 ms
import.css
347 ms
jquery.bxslider.css
374 ms
colorbox.css
391 ms
smartRollover.js
391 ms
AC_RunActiveContent.js
391 ms
reset.css
366 ms
module.css
393 ms
styles.css
621 ms
top.css
433 ms
content.css
606 ms
jquery.min.js
8 ms
jquery.slider.js
562 ms
slider.css
585 ms
jquery.bxslider.min.js
804 ms
jquery.colorbox.js
1106 ms
bnr_01.jpg
1678 ms
bnr_usedboatstore.jpg
1835 ms
bnr_kaitori.jpg
1470 ms
banner.jpg
1496 ms
bnr_marica.jpg
749 ms
header_bg.gif
189 ms
site-logo.gif
346 ms
shop-logo.gif
353 ms
gNav_bg.jpg
935 ms
gNav_home.jpg
525 ms
gNav_InlandSea.jpg
560 ms
gNav_rentalClub.jpg
712 ms
gNav_licenseClass.jpg
725 ms
gNav_usedBoat.jpg
871 ms
gNav_onlineShop.jpg
899 ms
gNav_marina.jpg
926 ms
gNav_maintenance.jpg
1077 ms
content_bg_home.jpg
3149 ms
image01.jpg
3335 ms
image02.jpg
2834 ms
image03.jpg
5058 ms
image04.jpg
5909 ms
image05.jpg
4240 ms
m_bnr.jpg
4117 ms
main_bg.gif
3492 ms
sec02_bg.gif
3686 ms
sec02_1_head_off.gif
3859 ms
sec02_1_image.jpg
4374 ms
sec02_3_head_off.gif
4203 ms
sec02_3_image.jpg
5808 ms
sec02_2_head_off.gif
4570 ms
sec02_2_image.jpg
4606 ms
sec02_point.jpg
4742 ms
sec02_4_head_off.gif
4959 ms
sec02_4_image.jpg
5122 ms
sec03_1.jpg
5602 ms
sec03_point.gif
5302 ms
sec03_2.jpg
5931 ms
news.html
5490 ms
ga.js
6 ms
__utm.gif
11 ms
__utm.gif
4 ms
staffblog.html
5494 ms
sec03_3.jpg
6209 ms
pickUp_head.gif
5621 ms
pickUp_image_01.jpg
5833 ms
pickUp_image_02.jpg
5864 ms
pickUp_image_03.jpg
6173 ms
pickUp_image_04.jpg
5972 ms
sec01_banner.jpg
6729 ms
banner_recruit.jpg
6201 ms
banner_trade-in.jpg
6239 ms
banner_onlineshop.jpg
6232 ms
banner_aboshiboatpark.jpg
6342 ms
page_top_btn.jpg
6108 ms
ft_address_tel.gif
6239 ms
ft_address_mail_head.gif
4551 ms
ft_address_btn.gif
4312 ms
footer_bg.jpg
4159 ms
ft_point.gif
4170 ms
point_ft_guide.jpg
3970 ms
bx_loader.gif
3962 ms
news_topics_head.gif
2282 ms
sec_point_arrow.gif
2304 ms
sec_point_circle.jpg
2341 ms
2016_03_14]011-thumb-50xauto-7918.jpg
1063 ms
IMG_6014-thumb-50xauto-7899.jpg
560 ms
IMGP1414_R-thumb-50xauto-7883.jpg
1863 ms
staff_diary_head.gif
2364 ms
print.css
1018 ms
seasea.jp 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
button, link, and menuitem elements do not have accessible names.
ARIA input fields do not have accessible names
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
Buttons do not have an accessible name
Links do not have a discernible name
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
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.
seasea.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
seasea.jp SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 doesn't use 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 Seasea.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 Seasea.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.
seasea.jp
Open Graph description is not detected on the main page of Seasea. 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: