Tools & Wizards About Us
nep.tw screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

nep.tw

鑽石家居礦泉水

Page Load Speed

11.2 sec in total

First Response

449 ms

Resources Loaded

10.4 sec

Page Rendered

323 ms

nep.tw screenshot

About Website

Welcome to nep.tw homepage info - get ready to check Nep best content right away, or after learning these important things about nep.tw

水，惠及萬物，我們應給予更高的尊崇。因此，DIAMOND對水的敬愛近乎瘋狂。我們把淨水器從一件工具精緻化，DIAMOND CORAL可能是全球首部精品水機。 Diamond透過代理形式直接銷售，減少經營成本，令客戶以最超值的價錢得到最好的產品及服務。同時，Diamond更為代理商提供一個創業商機，開拓個人事業，我們更會提供完善的訓練系統、銷售支援、客戶推廣活動等，協助代理創業，成就人生夢想。

Visit nep.tw

Key Findings

We analyzed Nep.tw page load time and found that the first response time was 449 ms and then it took 10.7 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

nep.tw performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value18.1 s

0/100

25%

SI (Speed Index)

Value14.2 s

1/100

10%

TBT (Total Blocking Time)

Value1,430 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.401

25/100

15%

TTI (Time to Interactive)

Value18.9 s

3/100

10%

Network Requests Diagram

main

449 ms

3104 ms

analytics.js

8 ms

index.php

1266 ms

index.php

1914 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 59% of them (13 requests) were addressed to the original Nep.tw, 14% (3 requests) were made to Google-analytics.com and 9% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Nep.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 217.5 kB (9%)

Content Size

2.3 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Nep.tw 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. 40% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 15.0 kB

  • Original 21.3 kB
  • After minification 20.9 kB
  • After compression 6.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. 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 15.0 kB or 71% of the original size.

Image Optimization

-5%

Potential reduce by 96.6 kB

  • Original 2.1 MB
  • After minification 2.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. Nep images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 105.9 kB

  • Original 155.9 kB
  • After minification 155.6 kB
  • After compression 50.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 105.9 kB or 68% of the original size.

Requests Breakdown

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

Requests Now

20

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

main

main

449 ms

3104 ms

analytics.js

analytics.js

8 ms

index.php

index.php

1266 ms

index.php

index.php

1914 ms

collect

collect

14 ms

lightbox.js

lightbox.js

953 ms

mediaelement-and-player.js

mediaelement-and-player.js

1302 ms

spotlight.js

spotlight.js

768 ms

diamond-logo.png

diamond-logo.png

881 ms

High-Value-Trade-In_E_June2015_OL-TW_C.jpg

High-Value-Trade-In_E_June2015_OL-TW_C.jpg

2955 ms

nav.png

nav.png

726 ms

collect

collect

712 ms

slideshow.js

slideshow.js

856 ms

plusone.js

plusone.js

168 ms

all.js

all.js

166 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

79 ms

156 ms

xd_arbiter.php

xd_arbiter.php

52 ms

xd_arbiter.php

xd_arbiter.php

70 ms

diamond-coral-contact.jpg

diamond-coral-contact.jpg

2349 ms

diamond-refined-coral-banner.jpg

diamond-refined-coral-banner.jpg

2085 ms

Accessibility Review

nep.tw accessibility score

89

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.

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

Links do not have a discernible name

Best Practices

nep.tw best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

nep.tw SEO score

92

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

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

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 Nep.tw 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 Nep.tw 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

nep.tw

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