Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

elegantsis.com

home | 傑本尼氏 | 手錶

Page Load Speed

19.4 sec in total

First Response

3 sec

Resources Loaded

15.5 sec

Page Rendered

896 ms

elegantsis.com screenshot

About Website

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

傑本尼氏 | 手錶

Visit elegantsis.com

Key Findings

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

Performance Metrics

elegantsis.com performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

25/100

10%

LCP (Largest Contentful Paint)

Value13.4 s

0/100

25%

SI (Speed Index)

Value18.2 s

0/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value1.424

0/100

15%

TTI (Time to Interactive)

Value3.9 s

88/100

10%

Network Requests Diagram

elegantsis.com

3022 ms

ai.master.css

567 ms

ai.master.js

571 ms

ai.fonts.css

575 ms

ai.grid.css

758 ms

Our browser made a total of 116 requests to load all elements on the main page. We found that 95% of them (110 requests) were addressed to the original Elegantsis.com, 1% (1 request) were made to Fonts.googleapis.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (5.6 sec) belongs to the original domain Elegantsis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (47%)

Content Size

2.4 MB

After Optimization

1.3 MB

In fact, the total size of Elegantsis.com main page is 2.4 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. 55% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 730.3 kB

  • Original 870.9 kB
  • After minification 849.2 kB
  • After compression 140.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 730.3 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 26.3 kB

  • Original 1.1 MB
  • After minification 1.0 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. Elegantsis images are well optimized though.

JavaScript Optimization

-80%

Potential reduce by 233.6 kB

  • Original 290.6 kB
  • After minification 179.0 kB
  • After compression 57.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 233.6 kB or 80% of the original size.

CSS Optimization

-86%

Potential reduce by 121.0 kB

  • Original 140.5 kB
  • After minification 113.1 kB
  • After compression 19.5 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. Elegantsis.com needs all CSS files to be minified and compressed as it can save up to 121.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 63 (56%)

Requests Now

112

After Optimization

49

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

Accessibility Review

elegantsis.com accessibility score

52

Accessibility Issues

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.

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

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

elegantsis.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

elegantsis.com SEO score

76

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Elegantsis.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Chinese language. Our system also found out that Elegantsis.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 data is detected on the main page of Elegantsis. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: