Report Summary

  • 0

    Performance

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

we-shop.net

Ecshop 繁體中文支援-原來如此

Page Load Speed

3.2 sec in total

First Response

442 ms

Resources Loaded

2.5 sec

Page Rendered

331 ms

we-shop.net screenshot

About Website

Welcome to we-shop.net homepage info - get ready to check We Shop best content for Taiwan right away, or after learning these important things about we-shop.net

使用功能齊全免費的 Ecshop網路購物系統,wordpress Blog 部落格,或搭建專業的企業網站,結合 RWD(Responsive Web Design) 響應式模板,與快速高效的PHP7+、SQLI資料庫,本站提供專職的技術支援,讓您在網路上能盡速佔有一席之地,是公司或企業網路行銷的最佳選擇,最省錢的網路創業... https://we-shop.net

Visit we-shop.net

Key Findings

We analyzed We-shop.net page load time and found that the first response time was 442 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

we-shop.net performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.3 s

3/100

10%

LCP (Largest Contentful Paint)

Value45.0 s

0/100

25%

SI (Speed Index)

Value28.8 s

0/100

10%

TBT (Total Blocking Time)

Value6,920 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.35

0/100

15%

TTI (Time to Interactive)

Value37.7 s

0/100

10%

Network Requests Diagram

we-shop.net

442 ms

reset.css

133 ms

style.css

134 ms

bootstrap.min.css

275 ms

style.css

207 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 62% of them (45 requests) were addressed to the original We-shop.net, 21% (15 requests) were made to Scontent.xx.fbcdn.net and 14% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain We-shop.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 516.6 kB (23%)

Content Size

2.3 MB

After Optimization

1.7 MB

In fact, the total size of We-shop.net 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. 35% of websites need less resources to load. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 41.7 kB

  • Original 53.0 kB
  • After minification 50.9 kB
  • After compression 11.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 41.7 kB or 79% of the original size.

Image Optimization

-8%

Potential reduce by 142.6 kB

  • Original 1.8 MB
  • After minification 1.6 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. We Shop images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 182.1 kB

  • Original 255.8 kB
  • After minification 210.8 kB
  • After compression 73.7 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 182.1 kB or 71% of the original size.

CSS Optimization

-82%

Potential reduce by 150.2 kB

  • Original 183.3 kB
  • After minification 177.8 kB
  • After compression 33.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. We-shop.net needs all CSS files to be minified and compressed as it can save up to 150.2 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (33%)

Requests Now

72

After Optimization

48

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

Accessibility Review

we-shop.net accessibility score

79

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

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

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

we-shop.net best practices score

58

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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

we-shop.net SEO score

100

Search Engine Optimization Advices

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 We-shop.net 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 We-shop.net 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 We Shop. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: