Tools & Wizards About Us
ourgame.com screenshot

Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

ourgame.com

联众游戏－快乐每一天！

Page Load Speed

10.4 sec in total

First Response

677 ms

Resources Loaded

9.4 sec

Page Rendered

234 ms

ourgame.com screenshot

About Website

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

联众大厅——“快乐每一天！” 联众大厅是提供棋牌休闲与竞技的综合网络休闲游戏平台，包含棋牌、麻将、休闲、大型网络游戏、社区互动娱乐等200余款游戏产品，为用户提供棋牌竞技、社区互动、游戏增值等多种服务。

Visit ourgame.com

Key Findings

We analyzed Ourgame.com page load time and found that the first response time was 677 ms and then it took 9.7 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

ourgame.com performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value5.5 s

19/100

25%

SI (Speed Index)

Value14.7 s

1/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

ourgame.com

677 ms

www.ourgame.com

86 ms

common.css

490 ms

swfobject.js

44 ms

ad_dl.js

938 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 79% of them (72 requests) were addressed to the original Ourgame.com, 8% (7 requests) were made to Image.ourgame.com and 5% (5 requests) were made to Ppxc010.ourgame.com. The less responsive or slowest element that took the longest time to load (5.3 sec) relates to the external source Hm.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 283.0 kB (26%)

Content Size

1.1 MB

After Optimization

789.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ourgame.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. 35% of websites need less resources to load. Images take 755.1 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 35.2 kB

  • Original 43.7 kB
  • After minification 32.2 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. This page needs HTML code to be minified as it can gain 11.5 kB, which is 26% 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 35.2 kB or 81% of the original size.

Image Optimization

-7%

Potential reduce by 54.0 kB

  • Original 755.1 kB
  • After minification 701.1 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. Ourgame images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 166.7 kB

  • Original 241.7 kB
  • After minification 224.4 kB
  • After compression 75.0 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 166.7 kB or 69% of the original size.

CSS Optimization

-84%

Potential reduce by 27.1 kB

  • Original 32.4 kB
  • After minification 25.9 kB
  • After compression 5.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. Ourgame.com needs all CSS files to be minified and compressed as it can save up to 27.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (36%)

Requests Now

89

After Optimization

57

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ourgame.com

ourgame.com

677 ms

www.ourgame.com

www.ourgame.com

86 ms

common.css

common.css

490 ms

swfobject.js

swfobject.js

44 ms

ad_dl.js

ad_dl.js

938 ms

ourgame_button.js

ourgame_button.js

1157 ms

list.aspx

list.aspx

993 ms

list.aspx

list.aspx

1031 ms

shownum.js

shownum.js

48 ms

ourgame_banner_righ.js

ourgame_banner_righ.js

1116 ms

cookie.js

cookie.js

1552 ms

array.js

array.js

386 ms

gameshow-https.js

gameshow-https.js

641 ms

our.js

our.js

66 ms

data_billboard.js

data_billboard.js

913 ms

data_game.js

data_game.js

866 ms

index_components.js

index_components.js

50 ms

7.js

7.js

51 ms

jquery-1.9.0.js

jquery-1.9.0.js

67 ms

bg_repeat.png

bg_repeat.png

481 ms

logo.png

logo.png

26 ms

icon.png

icon.png

461 ms

bg_banner.png

bg_banner.png

691 ms

ad_02a.jpg

ad_02a.jpg

26 ms

xianhuaka.gif

xianhuaka.gif

27 ms

icon_glob.png

icon_glob.png

34 ms

temp_02.gif

temp_02.gif

37 ms

temp_03.gif

temp_03.gif

35 ms

temp_13.jpg

temp_13.jpg

50 ms

temp_11.jpg

temp_11.jpg

53 ms

temp_12.jpg

temp_12.jpg

53 ms

jk.jpg

jk.jpg

67 ms

jf.jpg

jf.jpg

69 ms

webhall_icon.png

webhall_icon.png

494 ms

btn_banner.gif

btn_banner.gif

702 ms

billboard_prev.png

billboard_prev.png

693 ms

billboard_next.png

billboard_next.png

519 ms

autocue.png

autocue.png

741 ms

mask.png

mask.png

742 ms

fengkmj1.jpg

fengkmj1.jpg

947 ms

bg_title.png

bg_title.png

733 ms

bg_tab_repeat.gif

bg_tab_repeat.gif

766 ms

icon_new_title.gif

icon_new_title.gif

958 ms

bg_login_repeat.gif

bg_login_repeat.gif

930 ms

btn_login.png

btn_login.png

1192 ms

btn_other_login.gif

btn_other_login.gif

1006 ms

btn_registration.png

btn_registration.png

1211 ms

side_bar_min.jpg

side_bar_min.jpg

755 ms

index_application-https.js

index_application-https.js

851 ms

information-https.js

information-https.js

1025 ms

b336.jpg

b336.jpg

469 ms

icon336.jpg

icon336.jpg

190 ms

ddz.jpg

ddz.jpg

262 ms

icon334.jpg

icon334.jpg

388 ms

xuezhan2.png

xuezhan2.png

766 ms

xuezhan1.jpg

xuezhan1.jpg

517 ms

transparent.gif

transparent.gif

505 ms

billboard_pointer.png

billboard_pointer.png

491 ms

billboard_pointer_active.png

billboard_pointer_active.png

456 ms

billboard_prev_hover.png

billboard_prev_hover.png

709 ms

billboard_prev_disabled.png

billboard_prev_disabled.png

473 ms

billboard_next_hover.png

billboard_next_hover.png

887 ms

billboard_next_disabled.png

billboard_next_disabled.png

923 ms

jsonnews.asp

jsonnews.asp

857 ms

jsonnews.asp

jsonnews.asp

899 ms

jsonnews.asp

jsonnews.asp

903 ms

jsonnews.asp

jsonnews.asp

1077 ms

h.js

h.js

5284 ms

pointer.png

pointer.png

1145 ms

fmz.png

fmz.png

1208 ms

daren.png

daren.png

1274 ms

mjsj.png

mjsj.png

1529 ms

fkmj.png

fkmj.png

1314 ms

tq.png

tq.png

1713 ms

elsfk.png

elsfk.png

1615 ms

zdcr.png

zdcr.png

1710 ms

xzmj.png

xzmj.png

1764 ms

shmj.png

shmj.png

2030 ms

sdmj.png

sdmj.png

2003 ms

gdmj.png

gdmj.png

2087 ms

sj.png

sj.png

2200 ms

ddz.png

ddz.png

2186 ms

qp.png

qp.png

2226 ms

bh.png

bh.png

2491 ms

zgxq.png

zgxq.png

2523 ms

klwq.png

klwq.png

2553 ms

sgjq.png

sgjq.png

2648 ms

fxq.png

fxq.png

2672 ms

gamemenu_active.png

gamemenu_active.png

2723 ms

hm.gif

hm.gif

323 ms

icon_menu_on.gif

icon_menu_on.gif

481 ms

Accessibility Review

ourgame.com accessibility score

63

Accessibility Issues

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

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

ourgame.com SEO score

62

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

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

ourgame.com

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