Access jyacht.com. 精艇游艇网——中文游艇门户网站|买游艇|游艇交易平台

jyacht.com screenshot

65

Performance

Renders faster than
78% of other websites
41

Accessibility

Visual factors better than
that of 19% of websites
75

Best Practices

More advanced features
available than in
35% of websites
84

SEO

Google-friendlier than
52% of websites

First Response

677 ms

Resources Loaded

11.4 sec

Page Rendered

433 ms

jyacht.com screenshot

About Website

Click here to check amazing Jyacht content for China. Otherwise, check out these important facts you probably never knew about jyacht.com

精艇游艇网是面向全球中文用户的门户型游艇网站，内容涵盖游艇品牌、二手游艇、游艇码头、超级游艇、游艇买卖、游艇评赏等信息，是买游艇用户的必看资料库，也是游艇从业人士、游艇爱好者及所有关注游艇人士必看的游艇网。

Visit jyacht.com

Key Findings

We analyzed Jyacht.com page load time and found that the first response time was 677 ms and then it took 11.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

43/100

25%

SI (Speed Index)

Value6.7 s

36/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.196

63/100

15%

TTI (Time to Interactive)

Value4.5 s

83/100

10%

jyacht.com

677 ms

www.jyacht.com

1538 ms

zhcss2.css

226 ms

morwww.js

444 ms

zhjs.js

907 ms

Our browser made a total of 142 requests to load all elements on the main page. We found that 99% of them (140 requests) were addressed to the original Jyacht.com, 1% (2 requests) were made to Hm.baidu.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Jyacht.com.

Content Size

3.0 MB

After Optimization

2.9 MB

In fact, the total size of Jyacht.com main page is 3.0 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 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 105.2 kB

Original 121.4 kB
After minification 90.7 kB
After compression 16.2 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 30.7 kB, which is 25% 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 105.2 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 65.5 kB

Original 2.9 MB
After minification 2.8 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. Jyacht images are well optimized though.

JavaScript Optimization

-9%

Potential reduce by 4.3 kB

Original 47.2 kB
After minification 47.2 kB
After compression 43.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. This website has mostly compressed JavaScripts.

CSS Optimization

-12%

Potential reduce by 881 B

Original 7.4 kB
After minification 7.4 kB
After compression 6.6 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. Jyacht.com needs all CSS files to be minified and compressed as it can save up to 881 B or 12% of the original size.

Requests Now

140

After Optimization

140

The browser has sent 140 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jyacht. According to our analytics all requests are already optimized.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

These are opportunities to improve the interpretation of your content by users in different locales.

High

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

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

robots.txt is not valid

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

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

ZH
Language Claimed

N/A
Encoding

GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jyacht.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese 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 Jyacht.com main page’s claimed encoding is gb2312. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

jyacht.com

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