Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

inplus.tw

INPLUS-INPLUS 3D列印良品

Page Load Speed

5.9 sec in total

First Response

1.6 sec

Resources Loaded

3.8 sec

Page Rendered

470 ms

inplus.tw screenshot

About Website

Welcome to inplus.tw homepage info - get ready to check INPLUS best content for Taiwan right away, or after learning these important things about inplus.tw

INPLUS●3D列印良品

Visit inplus.tw

Key Findings

We analyzed Inplus.tw page load time and found that the first response time was 1.6 sec and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

inplus.tw performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value17.4 s

0/100

25%

SI (Speed Index)

Value7.1 s

30/100

10%

TBT (Total Blocking Time)

Value2,210 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value1.496

0/100

15%

TTI (Time to Interactive)

Value11.5 s

18/100

10%

Network Requests Diagram

inplus.tw

1641 ms

woocommerce-layout.css

132 ms

woocommerce.css

135 ms

style.css

198 ms

css

29 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 57% of them (70 requests) were addressed to the original Inplus.tw, 8% (10 requests) were made to Scontent.xx.fbcdn.net and 8% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Inplus.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 783.8 kB (40%)

Content Size

2.0 MB

After Optimization

1.2 MB

In fact, the total size of Inplus.tw main page is 2.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. 70% of websites need less resources to load. Images take 998.0 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 95.6 kB

  • Original 108.4 kB
  • After minification 98.8 kB
  • After compression 12.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 95.6 kB or 88% of the original size.

Image Optimization

-7%

Potential reduce by 69.7 kB

  • Original 998.0 kB
  • After minification 928.3 kB

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. INPLUS images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 221.2 kB

  • Original 410.7 kB
  • After minification 393.8 kB
  • After compression 189.5 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 221.2 kB or 54% of the original size.

CSS Optimization

-87%

Potential reduce by 397.3 kB

  • Original 458.0 kB
  • After minification 395.7 kB
  • After compression 60.7 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. Inplus.tw needs all CSS files to be minified and compressed as it can save up to 397.3 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (38%)

Requests Now

115

After Optimization

71

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

Accessibility Review

inplus.tw accessibility score

72

Accessibility Issues

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

Buttons do not have an accessible name

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

Best Practices

inplus.tw best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

inplus.tw SEO score

77

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

High

Document uses plugins

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 Inplus.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 Inplus.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

Open Graph data is detected on the main page of INPLUS. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: