Tools & Wizards About Us
pay.61.com screenshot

Report Summary

  • 59

    Performance

    Renders faster than
    75% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 50

    SEO

    Google-friendlier than
    18% of websites

pay.61.com

充值中心 - 淘米网

Page Load Speed

16.6 sec in total

First Response

2.1 sec

Resources Loaded

14.5 sec

Page Rendered

115 ms

pay.61.com screenshot

About Website

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

淘米网(www.61.com)是专为中国儿童打造的综合互动娱乐平台，为孩子们提供摩尔庄园、赛尔号、大玩国、哈奇小镇等丰富多彩、健康安全的互动娱乐产品，同时淘米网也是儿童健康安全上网的倡导者。米米卡和米币可以用于支付淘米的收费产品。

Visit pay.61.com

Key Findings

We analyzed Pay.61.com page load time and found that the first response time was 2.1 sec and then it took 14.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

pay.61.com performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

75/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

84/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.2 s

32/100

10%

Network Requests Diagram

pay.61.com

2066 ms

pay.css

5533 ms

global.css

8798 ms

service.css

5529 ms

account.css

5527 ms

Our browser made a total of 35 requests to load all elements on the main page. We found that 20% of them (7 requests) were addressed to the original Pay.61.com, 69% (24 requests) were made to Support-res.61.com and 6% (2 requests) were made to Resads.61.com. The less responsive or slowest element that took the longest time to load (10.1 sec) belongs to the original domain Pay.61.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 264.9 kB (60%)

Content Size

445.0 kB

After Optimization

180.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pay.61.com main page is 445.0 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. Javascripts take 258.0 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 13.0 kB

  • Original 18.4 kB
  • After minification 17.1 kB
  • After compression 5.4 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 13.0 kB or 71% of the original size.

Image Optimization

-10%

Potential reduce by 10.1 kB

  • Original 96.4 kB
  • After minification 86.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. Pay 61 images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 182.6 kB

  • Original 258.0 kB
  • After minification 230.2 kB
  • After compression 75.4 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 182.6 kB or 71% of the original size.

CSS Optimization

-82%

Potential reduce by 59.2 kB

  • Original 72.2 kB
  • After minification 64.9 kB
  • After compression 13.0 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. Pay.61.com needs all CSS files to be minified and compressed as it can save up to 59.2 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (29%)

Requests Now

34

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pay.61.com

pay.61.com

2066 ms

pay.css

pay.css

5533 ms

global.css

global.css

8798 ms

service.css

service.css

5529 ms

account.css

account.css

5527 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

9717 ms

base.js

base.js

10120 ms

jqUtils.js

jqUtils.js

968 ms

boxy.js

boxy.js

969 ms

public.js

public.js

2933 ms

common.js

common.js

3403 ms

jquery.flip.js

jquery.flip.js

984 ms

seer.png

seer.png

2626 ms

cplan.png

cplan.png

2650 ms

logo_game.png

logo_game.png

320 ms

repeat_nav.png

repeat_nav.png

270 ms

index_mibi.jpg

index_mibi.jpg

361 ms

ui_btn.png

ui_btn.png

287 ms

index_baoyue.jpg

index_baoyue.jpg

2186 ms

seer_index_adtips.png

seer_index_adtips.png

605 ms

service_nono_36.png

service_nono_36.png

623 ms

service_cplan_36.png

service_cplan_36.png

638 ms

service_gf_36.png

service_gf_36.png

661 ms

service_seer2_36.png

service_seer2_36.png

708 ms

service_hua_36.png

service_hua_36.png

955 ms

sprite_global.png

sprite_global.png

948 ms

index_duihuan.jpg

index_duihuan.jpg

1034 ms

service_xb_36.png

service_xb_36.png

1000 ms

mole.png

mole.png

1099 ms

service_ddt_36.png

service_ddt_36.png

1301 ms

repeat_box.png

repeat_box.png

1332 ms

sprite_ico.png

sprite_ico.png

1348 ms

footer_logo.png

footer_logo.png

1335 ms

h.js

h.js

1180 ms

hm.gif

hm.gif

329 ms

Accessibility Review

pay.61.com accessibility score

51

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

<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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

pay.61.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

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

pay.61.com SEO score

50

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pay.61.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Pay.61.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

pay.61.com

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