Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

funenet.com

船ネット - 中古船・中古艇情報

Page Load Speed

30.6 sec in total

First Response

855 ms

Resources Loaded

27.5 sec

Page Rendered

2.3 sec

funenet.com screenshot

About Website

Visit funenet.com now to see the best up-to-date Funenet content for Russia and also check out these interesting facts you probably never knew about funenet.com

中古船・中古艇(ボート・漁船・ヨット・水上バイク等)や、パーツのインターネット最大級の個人売買情報サイト『船ネット』です。中古船を買いたい方、売りたい方はぜひご相談ください!個人を問わず、日本全国のエリア担当が貴方のマリンライフをサポート致します。中古船・中古艇情報 | 船ネット

Visit funenet.com

Key Findings

We analyzed Funenet.com page load time and found that the first response time was 855 ms and then it took 29.7 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

funenet.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value20.5 s

0/100

25%

SI (Speed Index)

Value14.1 s

1/100

10%

TBT (Total Blocking Time)

Value4,100 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.0 s

3/100

10%

Network Requests Diagram

funenet.com

855 ms

style.css

387 ms

jquery-loader.js

383 ms

script.js

392 ms

tooltip.js

424 ms

Our browser made a total of 378 requests to load all elements on the main page. We found that 74% of them (279 requests) were addressed to the original Funenet.com, 6% (21 requests) were made to Static.xx.fbcdn.net and 5% (18 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (7.3 sec) belongs to the original domain Funenet.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (37%)

Content Size

4.8 MB

After Optimization

3.1 MB

In fact, the total size of Funenet.com main page is 4.8 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.3 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 208.9 kB

  • Original 240.8 kB
  • After minification 235.8 kB
  • After compression 31.8 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 208.9 kB or 87% of the original size.

Image Optimization

-33%

Potential reduce by 1.4 MB

  • Original 4.3 MB
  • After minification 2.9 MB

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, Funenet needs image optimization as it can save up to 1.4 MB or 33% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-38%

Potential reduce by 91.2 kB

  • Original 242.8 kB
  • After minification 235.1 kB
  • After compression 151.6 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 91.2 kB or 38% of the original size.

CSS Optimization

-81%

Potential reduce by 49.5 kB

  • Original 61.5 kB
  • After minification 53.5 kB
  • After compression 12.0 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. Funenet.com needs all CSS files to be minified and compressed as it can save up to 49.5 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 76 (20%)

Requests Now

373

After Optimization

297

The browser has sent 373 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funenet. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 40 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

funenet.com accessibility score

62

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

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

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

<html> element does not have a [lang] attribute

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

funenet.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

funenet.com SEO score

91

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Funenet.com 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 Funenet.com 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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Funenet. 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: