Tools & Wizards About Us
kingpaper.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

kingpaper.com

King Paper, global distributers of paper and liner board

Page Load Speed

1.7 sec in total

First Response

63 ms

Resources Loaded

1.2 sec

Page Rendered

469 ms

kingpaper.com screenshot

About Website

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

King Paper is a leader in the global distribution of selling and transporting paper products and liner board.

Visit kingpaper.com

Key Findings

We analyzed Kingpaper.com page load time and found that the first response time was 63 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

kingpaper.com performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value20.4 s

0/100

25%

SI (Speed Index)

Value8.1 s

21/100

10%

TBT (Total Blocking Time)

Value1,380 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0.192

64/100

15%

TTI (Time to Interactive)

Value18.0 s

3/100

10%

Network Requests Diagram

kingpaper.com

63 ms

www.kingpaper.com

102 ms

css2

139 ms

css

170 ms

bootstrap.min.css

146 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 41% of them (28 requests) were addressed to the original Kingpaper.com, 25% (17 requests) were made to Fonts.gstatic.com and 14% (10 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (394 ms) relates to the external source Amcharts.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 937.0 kB (35%)

Content Size

2.7 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kingpaper.com main page is 2.7 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. HTML takes 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 902.8 kB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 464.7 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 902.8 kB or 66% of the original size.

Image Optimization

-0%

Potential reduce by 5 B

  • Original 477.8 kB
  • After minification 477.7 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. King Paper images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 18.9 kB

  • Original 796.7 kB
  • After minification 796.7 kB
  • After compression 777.8 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. This website has mostly compressed JavaScripts.

CSS Optimization

-27%

Potential reduce by 15.3 kB

  • Original 55.7 kB
  • After minification 55.7 kB
  • After compression 40.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. Kingpaper.com needs all CSS files to be minified and compressed as it can save up to 15.3 kB or 27% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (88%)

Requests Now

48

After Optimization

6

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kingpaper.com

kingpaper.com

63 ms

www.kingpaper.com

www.kingpaper.com

102 ms

css2

css2

139 ms

css

css

170 ms

bootstrap.min.css

bootstrap.min.css

146 ms

icofont.min.css

icofont.min.css

76 ms

boxicons.min.css

boxicons.min.css

101 ms

venobox.css

venobox.css

98 ms

owl.carousel.min.css

owl.carousel.min.css

136 ms

animate.min.css

animate.min.css

107 ms

aos.css

aos.css

119 ms

font-awesome.min.css

font-awesome.min.css

136 ms

datatables.min.css

datatables.min.css

155 ms

responsive.dataTables.min.css

responsive.dataTables.min.css

189 ms

all.min.css

all.min.css

164 ms

fontawesome.min.css

fontawesome.min.css

159 ms

appcss

appcss

119 ms

style2.css

style2.css

122 ms

anime.min.js

anime.min.js

156 ms

modernizr

modernizr

210 ms

jquery.min.js

jquery.min.js

130 ms

app.js

app.js

155 ms

api.js

api.js

185 ms

owl.carousel.css

owl.carousel.css

168 ms

owl.theme.default.min.css

owl.theme.default.min.css

185 ms

owl.theme.green.min.css

owl.theme.green.min.css

184 ms

ammap.js

ammap.js

166 ms

worldHigh.js

worldHigh.js

394 ms

dark.js

dark.js

380 ms

bootstrap

bootstrap

150 ms

libjs

libjs

316 ms

jqueryval

jqueryval

149 ms

wow.min.js

wow.min.js

165 ms

mobile-nav.js

mobile-nav.js

165 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

315 ms

easing.min.js

easing.min.js

164 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

371 ms

venobox.min.js

venobox.min.js

370 ms

aos.js

aos.js

369 ms

owl.carousel.min.js

owl.carousel.min.js

312 ms

main.js

main.js

369 ms

appjs

appjs

365 ms

jquery.dataTables.min.js

jquery.dataTables.min.js

365 ms

datatables.min.js

datatables.min.js

365 ms

dataTables.responsive.min.js

dataTables.responsive.min.js

366 ms

recaptcha__en.js

recaptcha__en.js

213 ms

kp-logo-trans.png

kp-logo-trans.png

197 ms

KP-line-logo.png

KP-line-logo.png

196 ms

male-engineer.jpg

male-engineer.jpg

198 ms

pattern.png

pattern.png

200 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w-.ttf

202 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w-.ttf

240 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w-.ttf

248 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w-.ttf

273 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew-.ttf

271 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew-.ttf

272 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

249 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

247 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

270 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

272 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9aX8.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq6R9aX8.ttf

273 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9aX8.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq5Z9aX8.ttf

276 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq_p9aX8.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq_p9aX8.ttf

276 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq3p6aX8.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq3p6aX8.ttf

277 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6aX8.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jq0N6aX8.ttf

277 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR6aX8.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqyR6aX8.ttf

279 ms

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqw16aX8.ttf

JTUFjIg1_i6t8kCHKm459Wx7xQYXK0vOoz6jqw16aX8.ttf

274 ms

icofont.woff

icofont.woff

200 ms

fa-brands-400.woff

fa-brands-400.woff

119 ms

Accessibility Review

kingpaper.com accessibility score

71

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

[role]s are not contained by their required parent element

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Best Practices

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

kingpaper.com SEO score

78

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kingpaper.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 Kingpaper.com 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

kingpaper.com

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