Tools & Wizards About Us
lty888.cn screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 70

    SEO

    Google-friendlier than
    29% of websites

lty888.cn

元音改成都汽车音响改装店连锁官网-无损汽车隔音方案-成都市元音电子有限公司

Page Load Speed

72.7 sec in total

First Response

10.6 sec

Resources Loaded

61.6 sec

Page Rendered

490 ms

lty888.cn screenshot

About Website

Welcome to lty888.cn homepage info - get ready to check Lty 888 best content right away, or after learning these important things about lty888.cn

元音改总店成都汽车音响改装十余年技术老店，近三十家连锁多年荣获全国10大汽车音响改装店，数万台汽车音响隔音改装经验，丹麦丹拿品牌总代理商：惠威音响,德国rs、意大利诗芬尼 、法国劲浪、以色列摩雷、大白鲨汽车隔音、俄罗斯stp隔音,美国捷力、卡莱、优美声等国内外知名品牌，也是广大汽车音响“发烧友”的必选改装店。

Visit lty888.cn

Key Findings

We analyzed Lty888.cn page load time and found that the first response time was 10.6 sec and then it took 62.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 29 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

lty888.cn performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value14.7 s

1/100

10%

TBT (Total Blocking Time)

Value150 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.158

73/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

lty888.cn

10625 ms

9092 ms

main.css

5690 ms

jquery-1.2.6.min.js

4305 ms

jcarousellite.min.js

984 ms

Our browser made a total of 95 requests to load all elements on the main page. We found that 81% of them (77 requests) were addressed to the original Lty888.cn, 5% (5 requests) were made to Bdimg.share.baidu.com and 4% (4 requests) were made to Lxbjs.baidu.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Lty888.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 277.8 kB (13%)

Content Size

2.1 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lty888.cn main page is 2.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. 30% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 41.4 kB

  • Original 51.1 kB
  • After minification 39.6 kB
  • After compression 9.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 11.5 kB, which is 23% 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 41.4 kB or 81% of the original size.

Image Optimization

-10%

Potential reduce by 209.1 kB

  • Original 2.0 MB
  • After minification 1.8 MB

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. Lty 888 images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 27.2 kB

  • Original 44.1 kB
  • After minification 44.1 kB
  • After compression 16.9 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 27.2 kB or 62% of the original size.

CSS Optimization

-1%

Potential reduce by 17 B

  • Original 2.0 kB
  • After minification 2.0 kB
  • After compression 2.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. Lty888.cn has all CSS files already compressed.

Requests Breakdown

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

Requests Now

63

After Optimization

53

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lty888.cn

lty888.cn

10625 ms

9092 ms

main.css

main.css

5690 ms

jquery-1.2.6.min.js

jquery-1.2.6.min.js

4305 ms

jcarousellite.min.js

jcarousellite.min.js

984 ms

maizilin.js

maizilin.js

989 ms

index.php

index.php

806 ms

20130529105239127.jpg

20130529105239127.jpg

10277 ms

background.gif

background.gif

4840 ms

img1.gif

img1.gif

20329 ms

img1.png

img1.png

4740 ms

img6.png

img6.png

826 ms

img3.gif

img3.gif

4196 ms

img3.png

img3.png

3114 ms

img4.gif

img4.gif

1666 ms

img4.png

img4.png

3249 ms

img9.gif

img9.gif

4614 ms

20160401051022135.jpg

20160401051022135.jpg

4110 ms

20160328030518531.jpg

20160328030518531.jpg

12509 ms

20151105031213374.png

20151105031213374.png

15900 ms

20130820113644647.gif

20130820113644647.gif

6840 ms

20130820113739100.gif

20130820113739100.gif

6524 ms

20130820113835298.gif

20130820113835298.gif

6689 ms

20130820113920184.gif

20130820113920184.gif

8073 ms

20160408024744305.jpg

20160408024744305.jpg

16109 ms

20160407014109692.jpg

20160407014109692.jpg

20323 ms

20160406023245238.jpg

20160406023245238.jpg

9898 ms

20160331025427968.jpg

20160331025427968.jpg

15733 ms

20160330014812318.jpg

20160330014812318.jpg

18647 ms

20160329023636471.jpg

20160329023636471.jpg

20324 ms

20160325021249999.jpg

20160325021249999.jpg

18506 ms

20160324021248906.jpg

20160324021248906.jpg

20324 ms

20160323023615902.jpg

20160323023615902.jpg

20327 ms

20160322020028762.jpg

20160322020028762.jpg

20330 ms

20130909044629406.jpg

20130909044629406.jpg

20332 ms

20130902023143780.jpg

20130902023143780.jpg

20332 ms

20130823104706957.jpg

20130823104706957.jpg

20333 ms

20130823113438428.jpg

20130823113438428.jpg

20335 ms

20130823112502780.jpg

20130823112502780.jpg

20334 ms

20130823102742987.jpg

20130823102742987.jpg

20339 ms

31_1342151735.jpg

31_1342151735.jpg

20340 ms

27_1300710712%20(1).jpg

27_1300710712%20(1).jpg

20341 ms

20126605050486.jpg

20126605050486.jpg

20341 ms

20130514085933200.jpg

20130514085933200.jpg

20326 ms

h.js

h.js

736 ms

index.php

index.php

20500 ms

21.gif

21.gif

1987 ms

lxb.js

lxb.js

2241 ms

hm.gif

hm.gif

385 ms

stat.php

stat.php

1163 ms

20110516082720310.jpg

20110516082720310.jpg

19661 ms

stat.htm

stat.htm

253 ms

core.php

core.php

1039 ms

9.gif

9.gif

1108 ms

shell_v2.js

shell_v2.js

815 ms

log.gif

log.gif

436 ms

_l.js

_l.js

848 ms

20130909113409141.png

20130909113409141.png

20213 ms

20130909114807521.jpg

20130909114807521.jpg

20078 ms

logger.js

logger.js

359 ms

bds_s_v2.js

bds_s_v2.js

1071 ms

log.gif

log.gif

464 ms

20130909115138260.jpg

20130909115138260.jpg

20215 ms

app.gif

app.gif

1142 ms

20130806023937116.gif

20130806023937116.gif

18181 ms

20130902025245983.jpg

20130902025245983.jpg

19712 ms

20130902025422288.jpg

20130902025422288.jpg

17884 ms

20130902032023402.jpg

20130902032023402.jpg

20487 ms

bdsstyle.css

bdsstyle.css

384 ms

l6.gif

l6.gif

378 ms

20130916052817989.jpg

20130916052817989.jpg

18223 ms

20130903052119349.jpg

20130903052119349.jpg

19634 ms

20130903051855170.jpg

20130903051855170.jpg

18816 ms

20130911102451256.gif

20130911102451256.gif

20250 ms

20140421053357156.png

20140421053357156.png

20422 ms

20131119113631886.jpg

20131119113631886.jpg

14701 ms

1.jpg

1.jpg

10672 ms

img7.gif

img7.gif

14518 ms

img8.gif

img8.gif

11790 ms

img12.gif

img12.gif

19811 ms

img15.gif

img15.gif

13579 ms

img13.gif

img13.gif

19999 ms

20131229112114491.jpg

20131229112114491.jpg

9187 ms

img17.gif

img17.gif

10280 ms

img18.gif

img18.gif

11532 ms

img5.png

img5.png

10792 ms

img23.gif

img23.gif

11863 ms

img26.gif

img26.gif

15522 ms

img27.gif

img27.gif

12593 ms

img24.gif

img24.gif

13827 ms

img29.gif

img29.gif

17404 ms

img29_1.gif

img29_1.gif

15634 ms

img31.gif

img31.gif

19976 ms

img32.gif

img32.gif

17124 ms

img34.gif

img34.gif

16525 ms

Accessibility Review

lty888.cn accessibility score

65

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

lty888.cn 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

lty888.cn SEO score

70

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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

    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 Lty888.cn 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 Lty888.cn 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

lty888.cn

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