Tools & Wizards About Us
okinkon.com screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

okinkon.com

okinkon純台灣製造自動鉛筆

Page Load Speed

4.7 sec in total

First Response

493 ms

Resources Loaded

3.9 sec

Page Rendered

254 ms

okinkon.com screenshot

About Website

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

okinkon純台灣製造自動鉛筆唯一個專門販售與製造純台灣製造自動鉛筆 的公司

Visit okinkon.com

Key Findings

We analyzed Okinkon.com page load time and found that the first response time was 493 ms and then it took 4.2 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

okinkon.com performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value19.2 s

0/100

25%

SI (Speed Index)

Value12.0 s

4/100

10%

TBT (Total Blocking Time)

Value2,390 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.821

4/100

15%

TTI (Time to Interactive)

Value18.4 s

3/100

10%

Network Requests Diagram

okinkon.com

493 ms

www.okinkon.com

1210 ms

common-5500010b0eb5a10ac407ea577c5c067fc3609b82543046f9b2c67b2ab5842684.css

29 ms

application-9d7fef8627706a3af2b8082c1ea205223ce2fa62a01630248cb801060229a4b2.css

51 ms

paola-66a1ea46cee6965d87327bf485549ede7a866677915a8e923447ea603c314476.css

74 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 8% of them (2 requests) were addressed to the original Okinkon.com, 36% (9 requests) were made to Cdn.shoplineapp.com and 32% (8 requests) were made to Shoplineimg.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Img.shoplineapp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 191.7 kB (10%)

Content Size

1.8 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Okinkon.com main page is 1.8 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 111.4 kB

  • Original 148.9 kB
  • After minification 135.6 kB
  • After compression 37.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 111.4 kB or 75% of the original size.

Image Optimization

-15%

Potential reduce by 79.6 kB

  • Original 536.6 kB
  • After minification 457.0 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. Obviously, Okinkon needs image optimization as it can save up to 79.6 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 32 B

  • Original 1.0 MB
  • After minification 1.0 MB
  • After compression 1.0 MB

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. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 674 B

  • Original 120.1 kB
  • After minification 120.1 kB
  • After compression 119.4 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. Okinkon.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 8 (36%)

Requests Now

22

After Optimization

14

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

okinkon.com

okinkon.com

493 ms

www.okinkon.com

www.okinkon.com

1210 ms

common-5500010b0eb5a10ac407ea577c5c067fc3609b82543046f9b2c67b2ab5842684.css

common-5500010b0eb5a10ac407ea577c5c067fc3609b82543046f9b2c67b2ab5842684.css

29 ms

application-9d7fef8627706a3af2b8082c1ea205223ce2fa62a01630248cb801060229a4b2.css

application-9d7fef8627706a3af2b8082c1ea205223ce2fa62a01630248cb801060229a4b2.css

51 ms

paola-66a1ea46cee6965d87327bf485549ede7a866677915a8e923447ea603c314476.css

paola-66a1ea46cee6965d87327bf485549ede7a866677915a8e923447ea603c314476.css

74 ms

intl_tel_input-1d78fdf5.css

intl_tel_input-1d78fdf5.css

73 ms

bundle.tracing.min.js

bundle.tracing.min.js

22 ms

captureconsole.min.js

captureconsole.min.js

23 ms

currencies.js

currencies.js

88 ms

common-61f5c37a5afdd5656594c281055c824fbbc5d5c57115da2b3631763850f433bb.js

common-61f5c37a5afdd5656594c281055c824fbbc5d5c57115da2b3631763850f433bb.js

92 ms

shop-3d403f01faf2ebc1306e.js

shop-3d403f01faf2ebc1306e.js

259 ms

intl_tel_input-005d6313095581378a92.js

intl_tel_input-005d6313095581378a92.js

89 ms

paola-bg.png

paola-bg.png

1233 ms

x140.jpg

x140.jpg

819 ms

original.

original.

2240 ms

loader1.gif

loader1.gif

356 ms

400x.jpg

400x.jpg

1025 ms

400x.jpg

400x.jpg

866 ms

400x.jpg

400x.jpg

1091 ms

400x.jpg

400x.jpg

652 ms

400x.jpeg

400x.jpeg

878 ms

400x.jpeg

400x.jpeg

1128 ms

400x.jpg

400x.jpg

1095 ms

card_opay.png

card_opay.png

352 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

31 ms

Accessibility Review

okinkon.com accessibility score

69

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

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

High

Missing source maps for large first-party JavaScript

SEO Factors

okinkon.com SEO score

86

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Okinkon.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Okinkon.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

okinkon.com

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