Tools & Wizards About Us
maple-card.com screenshot

Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

maple-card.com

maple-card.com

Page Load Speed

44.5 sec in total

First Response

5.4 sec

Resources Loaded

38.6 sec

Page Rendered

574 ms

maple-card.com screenshot

About Website

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

www.maple-card.com

Visit maple-card.com

Key Findings

We analyzed Maple-card.com page load time and found that the first response time was 5.4 sec and then it took 39.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 20 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

maple-card.com performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

5/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.321

36/100

15%

TTI (Time to Interactive)

Value5.9 s

66/100

10%

Network Requests Diagram

maple-card.com

5369 ms

css.css

4796 ms

bodybg.jpg

467 ms

bodybg2.jpg

12015 ms

logobg.jpg

10372 ms

Our browser made a total of 85 requests to load all elements on the main page. We found that 66% of them (56 requests) were addressed to the original Maple-card.com, 24% (20 requests) were made to Qiao.baidu.com and 5% (4 requests) were made to P.qiao.baidu.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Maple-card.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 250.1 kB (24%)

Content Size

1.1 MB

After Optimization

813.5 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Maple-card.com main page is 1.1 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. 20% of websites need less resources to load. Images take 816.5 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 181.3 kB

  • Original 201.0 kB
  • After minification 165.3 kB
  • After compression 19.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. This page needs HTML code to be minified as it can gain 35.7 kB, which is 18% 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 181.3 kB or 90% of the original size.

Image Optimization

-4%

Potential reduce by 30.1 kB

  • Original 816.5 kB
  • After minification 786.4 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. Maple Card images are well optimized though.

CSS Optimization

-84%

Potential reduce by 38.7 kB

  • Original 46.1 kB
  • After minification 36.0 kB
  • After compression 7.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. Maple-card.com needs all CSS files to be minified and compressed as it can save up to 38.7 kB or 84% of the original size.

Requests Breakdown

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

Requests Now

64

After Optimization

43

  • Images
  • JavaScript
  • CSS

The browser has sent 64 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Maple Card. 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 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

maple-card.com

maple-card.com

5369 ms

css.css

css.css

4796 ms

bodybg.jpg

bodybg.jpg

467 ms

bodybg2.jpg

bodybg2.jpg

12015 ms

logobg.jpg

logobg.jpg

10372 ms

navbg.jpg

navbg.jpg

928 ms

nav2.jpg

nav2.jpg

5599 ms

navbg3.jpg

navbg3.jpg

3819 ms

navbg6-1.jpg

navbg6-1.jpg

4912 ms

msn.jpg

msn.jpg

1348 ms

qq.jpg

qq.jpg

2887 ms

liuyan.jpg

liuyan.jpg

3296 ms

2014112420491938886.jpg

2014112420491938886.jpg

5880 ms

2014112421242023370.jpg

2014112421242023370.jpg

5167 ms

fyindex_r8_c2.jpg

fyindex_r8_c2.jpg

19414 ms

2014121319482270826.jpg

2014121319482270826.jpg

14609 ms

2014121020335283275.jpg

2014121020335283275.jpg

11229 ms

2014121020334193145.jpg

2014121020334193145.jpg

7870 ms

2014121020332982462.jpg

2014121020332982462.jpg

9221 ms

2014121020331310649.jpg

2014121020331310649.jpg

13048 ms

201412102033297702.jpg

201412102033297702.jpg

11659 ms

2014121216315784639.jpg

2014121216315784639.jpg

16630 ms

2014121216432476359.jpg

2014121216432476359.jpg

14137 ms

2014121216482058206.jpg

2014121216482058206.jpg

17549 ms

20141212171270221.jpg

20141212171270221.jpg

19889 ms

201412121725878000.jpg

201412121725878000.jpg

19889 ms

2014121217292716798.jpg

2014121217292716798.jpg

18461 ms

2014121218241226087.jpg

2014121218241226087.jpg

19889 ms

2014121218331641659.jpg

2014121218331641659.jpg

19853 ms

2014121218292899990.jpg

2014121218292899990.jpg

19889 ms

201412131715022532.jpg

201412131715022532.jpg

19889 ms

201412131761944820.jpg

201412131761944820.jpg

19889 ms

2014121317121621573.jpg

2014121317121621573.jpg

19889 ms

2014121317221437403.jpg

2014121317221437403.jpg

19890 ms

2014121317284267338.jpg

2014121317284267338.jpg

19890 ms

2014121317563896639.jpg

2014121317563896639.jpg

19889 ms

201412131814845875.jpg

201412131814845875.jpg

19889 ms

201412131863312574.jpg

201412131863312574.jpg

19819 ms

h.js

h.js

1934 ms

201412131883728035.jpg

201412131883728035.jpg

20427 ms

201412131822159690.jpg

201412131822159690.jpg

19966 ms

201412131910492416.jpg

201412131910492416.jpg

19544 ms

b.js

b.js

751 ms

h.js

h.js

19771 ms

hm.gif

hm.gif

770 ms

bsl.js

bsl.js

2334 ms

2014121319413638110.jpg

2014121319413638110.jpg

20005 ms

2014121319141278316.jpg

2014121319141278316.jpg

19076 ms

2014121319332271851.jpg

2014121319332271851.jpg

19362 ms

2014121319253223398.jpg

2014121319253223398.jpg

19981 ms

fyindex_r13_c10.jpg

fyindex_r13_c10.jpg

18108 ms

Enter.php

Enter.php

854 ms

main_icon_invite_mess_api.js

main_icon_invite_mess_api.js

10344 ms

main.css

main.css

761 ms

fix.css

fix.css

933 ms

version.js

version.js

1383 ms

indexbtbg1.jpg

indexbtbg1.jpg

17038 ms

indexphone.jpg

indexphone.jpg

20011 ms

indexbtbg.jpg

indexbtbg.jpg

15144 ms

pan4_r10_c5.jpg

pan4_r10_c5.jpg

14226 ms

pan4_r10_c7.jpg

pan4_r10_c7.jpg

13314 ms

fyindex_r6_c2.gif

fyindex_r6_c2.gif

13463 ms

fyindex_r10_c2.jpg

fyindex_r10_c2.jpg

20231 ms

fen.jpg

fen.jpg

11892 ms

fen2.jpg

fen2.jpg

11869 ms

fyindex_r12_c7.jpg

fyindex_r12_c7.jpg

10283 ms

08.png

08.png

2888 ms

m-webim-lite.css

m-webim-lite.css

436 ms

m-webim-lite.js

m-webim-lite.js

1776 ms

Refresh.php

Refresh.php

449 ms

08.png

08.png

3365 ms

12.png

12.png

5869 ms

icon.png

icon.png

2080 ms

icon_close.png

icon_close.png

2654 ms

stat.gif

stat.gif

2611 ms

04.png

04.png

4738 ms

mess-text.png

mess-text.png

4158 ms

04_normal.png

04_normal.png

3315 ms

mess.gif

mess.gif

7605 ms

04_send_normal.png

04_send_normal.png

5908 ms

btn.png

btn.png

4390 ms

09_big.png

09_big.png

5901 ms

btn.png

btn.png

3016 ms

Refresh.php

Refresh.php

348 ms

Refresh.php

Refresh.php

1163 ms

Accessibility Review

maple-card.com accessibility score

67

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

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

maple-card.com best practices score

58

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

High

Browser errors were logged to the console

SEO Factors

maple-card.com SEO score

83

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

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Maple-card.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Maple-card.com main page’s claimed encoding is gb2312. 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

maple-card.com

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