Tools & Wizards About Us
iboxpay.com screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

iboxpay.com

盒子科技-构建互联互通的数字化商业服务开放生态

Page Load Speed

52.4 sec in total

First Response

1.7 sec

Resources Loaded

50.6 sec

Page Rendered

168 ms

iboxpay.com screenshot

About Website

Welcome to iboxpay.com homepage info - get ready to check Iboxpay best content for China right away, or after learning these important things about iboxpay.com

深圳盒子信息科技有限公司成立于2011年，注册资本为人民币51,680万元，盒子科技唯一官方客服热线电话：10109888，是一家专注于为商户提供互联互通的数字化商业服务解决方案，助力企业及商户实现数字化转型升级的国家高新技术企业。

Visit iboxpay.com

Key Findings

We analyzed Iboxpay.com page load time and found that the first response time was 1.7 sec and then it took 50.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 29 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

iboxpay.com performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value12.8 s

2/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.3 s

12/100

10%

Network Requests Diagram

iboxpay.com

1669 ms

www.iboxpay.com

8439 ms

theme.min.css

6122 ms

bootstrap-responsive.min.css

1796 ms

font-awesome.min.css

11554 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 85% of them (45 requests) were addressed to the original Iboxpay.com, 6% (3 requests) were made to Hm.baidu.com and 4% (2 requests) were made to Szcert.ebs.org.cn. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Iboxpay.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 73.7 kB (72%)

Content Size

102.4 kB

After Optimization

28.7 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Iboxpay.com main page is 102.4 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. 15% of websites need less resources to load. CSS take 78.0 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 15.4 kB

  • Original 21.5 kB
  • After minification 21.0 kB
  • After compression 6.1 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 15.4 kB or 72% of the original size.

JavaScript Optimization

-63%

Potential reduce by 1.8 kB

  • Original 2.8 kB
  • After minification 2.5 kB
  • After compression 1.1 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 1.8 kB or 63% of the original size.

CSS Optimization

-72%

Potential reduce by 56.5 kB

  • Original 78.0 kB
  • After minification 61.7 kB
  • After compression 21.5 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. Iboxpay.com needs all CSS files to be minified and compressed as it can save up to 56.5 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 14 (67%)

Requests Now

21

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

iboxpay.com

iboxpay.com

1669 ms

www.iboxpay.com

www.iboxpay.com

8439 ms

theme.min.css

theme.min.css

6122 ms

bootstrap-responsive.min.css

bootstrap-responsive.min.css

1796 ms

font-awesome.min.css

font-awesome.min.css

11554 ms

style.css

style.css

6560 ms

animate.css

animate.css

5163 ms

slippry.css

slippry.css

4569 ms

jquery.js

jquery.js

20455 ms

wind.js

wind.js

1213 ms

wow.min.js

wow.min.js

4313 ms

bootstrap.min.js

bootstrap.min.js

1532 ms

frontend.js

frontend.js

5337 ms

uaredirect.js

uaredirect.js

689 ms

count.js

count.js

1839 ms

slippry.min.js

slippry.min.js

4231 ms

govicon.js

govicon.js

1148 ms

hm.js

hm.js

1830 ms

logo.png

logo.png

4985 ms

weixin_qrcode.png

weixin_qrcode.png

6010 ms

glyphicons-halflings.png

glyphicons-halflings.png

5126 ms

57032b1a0f95c.jpg

57032b1a0f95c.jpg

19831 ms

56de2d7e6eaab.jpg

56de2d7e6eaab.jpg

19832 ms

565eb3d2b9f87.jpg

565eb3d2b9f87.jpg

19833 ms

563724bdd6f75.jpg

563724bdd6f75.jpg

19834 ms

55d682ba52352.png

55d682ba52352.png

19835 ms

55d43f18add9d.jpg

55d43f18add9d.jpg

19835 ms

55d58e151b9e1.png

55d58e151b9e1.png

19835 ms

56e678a48c8f5.jpg

56e678a48c8f5.jpg

19835 ms

pa1.png

pa1.png

19835 ms

pa2.png

pa2.png

19835 ms

pa3.png

pa3.png

19835 ms

pa4.png

pa4.png

19835 ms

pa5.png

pa5.png

19835 ms

pa6.png

pa6.png

19833 ms

pa7.png

pa7.png

19833 ms

pa8.png

pa8.png

19835 ms

pa9.png

pa9.png

19849 ms

pa10.png

pa10.png

19849 ms

pa12.png

pa12.png

19848 ms

au1.png

au1.png

19849 ms

au2.png

au2.png

19849 ms

au3.png

au3.png

19848 ms

au4.png

au4.png

19849 ms

au5.png

au5.png

19849 ms

au6.png

au6.png

19849 ms

au7.png

au7.png

19848 ms

au8.png

au8.png

19849 ms

font_1449140313_8410203.woff

font_1449140313_8410203.woff

517 ms

hm.gif

hm.gif

379 ms

hm.js

hm.js

19871 ms

govIcon.gif

govIcon.gif

3976 ms

iplookup.php

iplookup.php

1657 ms

Accessibility Review

iboxpay.com accessibility score

52

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

iboxpay.com best practices score

67

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

iboxpay.com SEO score

67

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

High

robots.txt is not valid

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iboxpay.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Iboxpay.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

iboxpay.com

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