Tools & Wizards About Us
smile.com.tw screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

smile.com.tw

Page Load Speed

3.4 sec in total

First Response

414 ms

Resources Loaded

2.3 sec

Page Rendered

664 ms

smile.com.tw screenshot

About Website

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

葡眾,康貝兒乳酸菌 獨立經銷商,lp33益生菌訂購,葡眾樂亦康,阿德比,新表飛鳴,康貝兒,995超級營養液,樟芝益,樟芝王,欣悅康,康貝兒益生菌,康貝兒乳酸菌價格,葡萄王康貝兒乳酸菌哪裡買,康貝兒乳酸菌經銷商,康貝兒乳酸菌多少錢,葡眾餐包、衛傑、愛益、康貝寧、貝力耐、清明亮、迪康、力盛、和悅、葡眾貝納Q10、永生福朗、葡眾寧康福、雅雅軟膏,葡眾企業,葡萄王益菌王,葡萄王樟芝王,葡萄王靈芝王,葡萄王...

Visit smile.com.tw

Key Findings

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

Performance Metrics

smile.com.tw performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value5.8 s

49/100

10%

TBT (Total Blocking Time)

Value1,130 ms

23/100

30%

CLS (Cumulative Layout Shift)

Value0.79

5/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

smile.com.tw

414 ms

www.smile.com.tw

568 ms

kiloinfo.css

121 ms

adsbygoogle.js

5 ms

contactus.gif

182 ms

Our browser made a total of 78 requests to load all elements on the main page. We found that 35% of them (27 requests) were addressed to the original Smile.com.tw, 9% (7 requests) were made to Tpc.googlesyndication.com and 8% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (568 ms) belongs to the original domain Smile.com.tw.

Page Optimization Overview & Recommendations

Page size can be reduced by 255.2 kB (45%)

Content Size

571.3 kB

After Optimization

316.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Smile.com.tw main page is 571.3 kB. 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. Javascripts take 347.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 58.2 kB

  • Original 72.1 kB
  • After minification 62.7 kB
  • After compression 14.0 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 9.5 kB, which is 13% 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 58.2 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 7.6 kB

  • Original 150.0 kB
  • After minification 142.5 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. Smile images are well optimized though.

JavaScript Optimization

-54%

Potential reduce by 188.2 kB

  • Original 347.4 kB
  • After minification 347.3 kB
  • After compression 159.3 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 188.2 kB or 54% of the original size.

CSS Optimization

-76%

Potential reduce by 1.3 kB

  • Original 1.7 kB
  • After minification 1.4 kB
  • After compression 400 B

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. Smile.com.tw needs all CSS files to be minified and compressed as it can save up to 1.3 kB or 76% of the original size.

Requests Breakdown

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

Requests Now

68

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

smile.com.tw

smile.com.tw

414 ms

www.smile.com.tw

www.smile.com.tw

568 ms

kiloinfo.css

kiloinfo.css

121 ms

adsbygoogle.js

adsbygoogle.js

5 ms

contactus.gif

contactus.gif

182 ms

pay-7-11.gif

pay-7-11.gif

69 ms

logo.gif

logo.gif

67 ms

butdown.jpg

butdown.jpg

67 ms

lefttop.jpg

lefttop.jpg

66 ms

butbac.jpg

butbac.jpg

300 ms

pay-mastercard.gif

pay-mastercard.gif

299 ms

pay-visa.gif

pay-visa.gif

300 ms

butmiddle.jpg

butmiddle.jpg

298 ms

leftback.jpg

leftback.jpg

300 ms

products-10030a.jpg

products-10030a.jpg

301 ms

righttop.jpg

righttop.jpg

300 ms

ad007.gif

ad007.gif

301 ms

ad009.jpg

ad009.jpg

304 ms

join.gif

join.gif

301 ms

ad.gif

ad.gif

371 ms

rightback.jpg

rightback.jpg

301 ms

sinopac.png

sinopac.png

305 ms

pic.jpg

pic.jpg

305 ms

rightmiddle.jpg

rightmiddle.jpg

305 ms

payment.gif

payment.gif

337 ms

down.jpg

down.jpg

366 ms

bg.gif

bg.gif

366 ms

ca-pub-7613824944770173.js

ca-pub-7613824944770173.js

57 ms

zrt_lookup.html

zrt_lookup.html

45 ms

show_ads_impl.js

show_ads_impl.js

57 ms

pay-7-11.gif

pay-7-11.gif

306 ms

ads

ads

318 ms

osd.js

osd.js

36 ms

ads

ads

282 ms

ads

ads

246 ms

119 ms

adj

adj

67 ms

beacon

beacon

54 ms

css

css

76 ms

m_js_controller.js

m_js_controller.js

43 ms

abg.js

abg.js

45 ms

nessie_icon_magazine_black.png

nessie_icon_magazine_black.png

29 ms

s

s

18 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

30 ms

nessie_icon_magazine_white.png

nessie_icon_magazine_white.png

10 ms

x_button_blue2.png

x_button_blue2.png

11 ms

click%253Fd%253DAPEucNWmLvCyLXU_ZI_rC17UxTRLfcX7uibn-Pe9lhVCZvAaayqUDWQ_3T4HZa55SelsIWSNASpMSK9bOTOQQk4ekYJXzgu-ZQ%2526r1%253D;ord=1458285834;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=

click%253Fd%253DAPEucNWmLvCyLXU_ZI_rC17UxTRLfcX7uibn-Pe9lhVCZvAaayqUDWQ_3T4HZa55SelsIWSNASpMSK9bOTOQQk4ekYJXzgu-ZQ%2526r1%253D;ord=1458285834;dc_lat=;dc_rdid=;tag_for_child_directed_treatment=

109 ms

verify_selector.js

verify_selector.js

179 ms

blank.gif

blank.gif

182 ms

beacon.js

beacon.js

59 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

22 ms

k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf

k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf

67 ms

cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf

cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf

70 ms

DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf

DXI1ORHCpsQm3Vp6mXoaTZS3E-kSBmtLoNJPDtbj2Pk.ttf

72 ms

html_inpage_rendering_lib_200_120.js

html_inpage_rendering_lib_200_120.js

35 ms

verifyr.js

verifyr.js

29 ms

0

0

73 ms

bg.png

bg.png

29 ms

surly.js

surly.js

33 ms

adchoices.en.png

adchoices.en.png

65 ms

ba.html

ba.html

6 ms

pixel

pixel

28 ms

4.gif

4.gif

17 ms

lidar.js

lidar.js

17 ms

sbhK2lTE.js

sbhK2lTE.js

16 ms

4311.js

4311.js

19 ms

cTrvNaRi.html

cTrvNaRi.html

10 ms

pixel

pixel

44 ms

pixel

pixel

45 ms

setuid

setuid

50 ms

sd

sd

5 ms

box_19_top-right.png

box_19_top-right.png

17 ms

ci.png

ci.png

18 ms

ui

ui

74 ms

index.html

index.html

27 ms

css

css

16 ms

Enabler_01_86.js

Enabler_01_86.js

7 ms

V86VyqXbc09Sss3BPsMj1yZ2oysoEQEeKwjgmXLRnTc.ttf

V86VyqXbc09Sss3BPsMj1yZ2oysoEQEeKwjgmXLRnTc.ttf

4 ms

Accessibility Review

smile.com.tw accessibility score

63

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

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

<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

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

Best Practices

smile.com.tw best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Page has valid source maps

SEO Factors

smile.com.tw SEO score

58

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

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

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 Smile.com.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 Smile.com.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

smile.com.tw

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