Tools & Wizards About Us
111ttt.com screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

111ttt.com

麦草音乐|交谊舞曲|要听舞曲

Page Load Speed

16.3 sec in total

First Response

812 ms

Resources Loaded

15 sec

Page Rendered

445 ms

111ttt.com screenshot

About Website

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

麦草音乐,交谊舞曲,要听舞曲网为广大跳舞爱好者与爱听舞曲的网友提供最好听的舞曲大全、舞曲下载、收录的舞曲以质量为本,我们一直坚持为广场舞和舞厅行业舔砖加瓦

Visit 111ttt.com

Key Findings

We analyzed 111ttt.com page load time and found that the first response time was 812 ms and then it took 15.5 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

111ttt.com performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.86

4/100

15%

TTI (Time to Interactive)

Value7.4 s

48/100

10%

Network Requests Diagram

111ttt.com

812 ms

www.111ttt.com

807 ms

index.css

1337 ms

common.js

993 ms

ds.js

1887 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 22% of them (10 requests) were addressed to the original 111ttt.com, 40% (18 requests) were made to Db-cache.t57.cn and 13% (6 requests) were made to Bdimg.share.baidu.com. The less responsive or slowest element that took the longest time to load (11.3 sec) relates to the external source P.tanx.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 277.9 kB (58%)

Content Size

480.4 kB

After Optimization

202.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 111ttt.com main page is 480.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. 20% of websites need less resources to load. Javascripts take 344.2 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 37.2 kB

  • Original 50.3 kB
  • After minification 49.8 kB
  • After compression 13.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 37.2 kB or 74% of the original size.

Image Optimization

-2%

Potential reduce by 1.8 kB

  • Original 74.5 kB
  • After minification 72.7 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. 111 Ttt images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 232.0 kB

  • Original 344.2 kB
  • After minification 340.2 kB
  • After compression 112.2 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 232.0 kB or 67% of the original size.

CSS Optimization

-61%

Potential reduce by 7.0 kB

  • Original 11.4 kB
  • After minification 10.7 kB
  • After compression 4.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. 111ttt.com needs all CSS files to be minified and compressed as it can save up to 7.0 kB or 61% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (56%)

Requests Now

43

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

111ttt.com

111ttt.com

812 ms

www.111ttt.com

www.111ttt.com

807 ms

index.css

index.css

1337 ms

common.js

common.js

993 ms

ds.js

ds.js

1887 ms

gg_index.js

gg_index.js

1119 ms

jquery.js

jquery.js

3063 ms

jquery.menu.js

jquery.menu.js

1351 ms

t.js

t.js

4 ms

topbg.gif

topbg.gif

433 ms

logo.png

logo.png

958 ms

head.png

head.png

2175 ms

i_desk.png

i_desk.png

868 ms

i_fav.gif

i_fav.gif

873 ms

I_Login.html

I_Login.html

486 ms

index.html

index.html

229 ms

h.png

h.png

2137 ms

dh.png

dh.png

1218 ms

dx.png

dx.png

1596 ms

jquery.js

jquery.js

3142 ms

bg.png

bg.png

2801 ms

autoplay.js

autoplay.js

5 ms

autoplaydata.js

autoplaydata.js

3393 ms

stat.php

stat.php

1763 ms

head.png

head.png

4 ms

qq_login.png

qq_login.png

5 ms

250x250.htm

250x250.htm

216 ms

ex

ex

11255 ms

stat.php

stat.php

2067 ms

hm.js

hm.js

2079 ms

loading.gif

loading.gif

446 ms

sj.png

sj.png

1027 ms

sj.png

sj.png

47 ms

stat.htm

stat.htm

262 ms

core.php

core.php

762 ms

core.php

core.php

752 ms

stat.htm

stat.htm

228 ms

hm.gif

hm.gif

1136 ms

shell_v2.js

shell_v2.js

1449 ms

logger.js

logger.js

264 ms

bds_s_v2.js

bds_s_v2.js

1051 ms

bdsstyle.css

bdsstyle.css

264 ms

getnum

getnum

946 ms

is.png

is.png

272 ms

sc.png

sc.png

269 ms

Accessibility Review

111ttt.com accessibility score

65

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

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

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

111ttt.com best practices score

75

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

111ttt.com SEO score

77

Search Engine Optimization Advices

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 111ttt.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 111ttt.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

111ttt.com

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