Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

Page Load Speed

67.3 sec in total

First Response

16.9 sec

Resources Loaded

49.8 sec

Page Rendered

625 ms

88.com screenshot

About Website

Click here to check amazing 88 content for China. Otherwise, check out these important facts you probably never knew about 88.com

Visit 88.com

Key Findings

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

Performance Metrics

88.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.3 s

0/100

25%

SI (Speed Index)

Value15.1 s

1/100

10%

TBT (Total Blocking Time)

Value840 ms

34/100

30%

CLS (Cumulative Layout Shift)

Value0.275

44/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

Network Requests Diagram

index.asp

16876 ms

2015_org.css

5488 ms

commonx.css

20229 ms

jquery-1.3.2.min.js

11060 ms

common.201208.js

1917 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that all of those requests were addressed to 88.com and no external sources were called. The less responsive or slowest element that took the longest time to load (20.2 sec) belongs to the original domain 88.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 51.5 kB (70%)

Content Size

73.9 kB

After Optimization

22.3 kB

In fact, the total size of 88.com main page is 73.9 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. HTML takes 48.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 40.0 kB

  • Original 48.5 kB
  • After minification 46.8 kB
  • After compression 8.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 40.0 kB or 82% of the original size.

Image Optimization

-12%

Potential reduce by 1.5 kB

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

JavaScript Optimization

-66%

Potential reduce by 4.1 kB

  • Original 6.2 kB
  • After minification 4.9 kB
  • After compression 2.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 4.1 kB or 66% of the original size.

CSS Optimization

-82%

Potential reduce by 6.0 kB

  • Original 7.3 kB
  • After minification 4.2 kB
  • After compression 1.3 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. 88.com needs all CSS files to be minified and compressed as it can save up to 6.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (50%)

Requests Now

24

After Optimization

12

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

Accessibility Review

88.com accessibility score

63

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

Form elements do not have associated labels

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

88.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

88.com SEO score

77

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

    ZH

  • Language Claimed

    N/A

  • Encoding

    GB2312

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

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