Tools & Wizards About Us
lh168.net screenshot

Report Summary

  • 0

    Performance

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 0

    Best Practices

  • 85

    SEO

    Google-friendlier than
    56% of websites

lh168.net

临海论坛,焦点新闻,今日临海

Page Load Speed

13.8 sec in total

First Response

1.9 sec

Resources Loaded

11.6 sec

Page Rendered

241 ms

lh168.net screenshot

About Website

Welcome to lh168.net homepage info - get ready to check Lh 168 best content for China right away, or after learning these important things about lh168.net

临海论坛临海每日发生的焦点新闻,临海在线

Visit lh168.net

Key Findings

We analyzed Lh168.net page load time and found that the first response time was 1.9 sec and then it took 11.9 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

lh168.net performance score

0

Network Requests Diagram

lh168.net

1943 ms

style.css

1041 ms

jquery-1.11.0.min.js

2738 ms

jquery.KinSlideshow-1.2.1.min.js

757 ms

SlidesStyleIndex.css

888 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 82% of them (49 requests) were addressed to the original Lh168.net, 5% (3 requests) were made to Hm.baidu.com and 3% (2 requests) were made to Img.cxmx.com.cn. The less responsive or slowest element that took the longest time to load (7.5 sec) relates to the external source Idinfo.zjaic.gov.cn.

Page Optimization Overview & Recommendations

Page size can be reduced by 244.0 kB (43%)

Content Size

566.3 kB

After Optimization

322.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lh168.net main page is 566.3 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. 25% of websites need less resources to load. Images take 268.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 50.3 kB

  • Original 61.3 kB
  • After minification 53.9 kB
  • After compression 11.0 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 7.4 kB, which is 12% 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 50.3 kB or 82% of the original size.

Image Optimization

-13%

Potential reduce by 33.8 kB

  • Original 268.4 kB
  • After minification 234.5 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, Lh 168 needs image optimization as it can save up to 33.8 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-65%

Potential reduce by 129.9 kB

  • Original 200.4 kB
  • After minification 198.4 kB
  • After compression 70.5 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 129.9 kB or 65% of the original size.

CSS Optimization

-83%

Potential reduce by 30.0 kB

  • Original 36.2 kB
  • After minification 32.7 kB
  • After compression 6.2 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. Lh168.net needs all CSS files to be minified and compressed as it can save up to 30.0 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (44%)

Requests Now

59

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 59 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lh 168. 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.

Network Requests Diagram

lh168.net

lh168.net

1943 ms

style.css

style.css

1041 ms

jquery-1.11.0.min.js

jquery-1.11.0.min.js

2738 ms

jquery.KinSlideshow-1.2.1.min.js

jquery.KinSlideshow-1.2.1.min.js

757 ms

SlidesStyleIndex.css

SlidesStyleIndex.css

888 ms

33108200001959.js

33108200001959.js

1230 ms

zxapp.jpg

zxapp.jpg

4887 ms

common_101_icon.jpg

common_101_icon.jpg

2207 ms

common_1_icon.jpg

common_1_icon.jpg

2224 ms

common_4522_icon.jpg

common_4522_icon.jpg

4069 ms

common_4523_icon.jpg

common_4523_icon.jpg

2447 ms

common_11_icon.jpg

common_11_icon.jpg

3919 ms

common_116_icon.jpg

common_116_icon.jpg

3602 ms

common_67_icon.jpg

common_67_icon.jpg

2900 ms

common_52_icon.jpg

common_52_icon.jpg

3221 ms

common_55_icon.jpg

common_55_icon.jpg

3346 ms

common_671_icon.jpg

common_671_icon.jpg

3557 ms

common_4490_icon.jpg

common_4490_icon.jpg

5382 ms

common_28_icon.jpg

common_28_icon.jpg

3894 ms

common_1041_icon.jpg

common_1041_icon.jpg

3936 ms

common_10_icon.jpg

common_10_icon.jpg

4232 ms

common_80_icon.jpg

common_80_icon.jpg

5539 ms

common_12_icon.png

common_12_icon.png

4270 ms

sky01.jpg

sky01.jpg

349 ms

sky02.jpg

sky02.jpg

341 ms

sky03.jpg

sky03.jpg

370 ms

indexbar.gif

indexbar.gif

656 ms

gygg.jpg

gygg.jpg

4567 ms

sky17.jpg

sky17.jpg

679 ms

3.jpg

3.jpg

686 ms

20140910-2.jpg

20140910-2.jpg

1375 ms

sky00.jpg

sky00.jpg

730 ms

sky06.jpg

sky06.jpg

998 ms

sky07.jpg

sky07.jpg

1004 ms

sky08.jpg

sky08.jpg

1012 ms

nav_listbg.png

nav_listbg.png

1090 ms

head_bg.png

head_bg.png

1325 ms

sky16.jpg

sky16.jpg

1310 ms

home_1.jpg

home_1.jpg

1309 ms

home_2.jpg

home_2.jpg

1417 ms

home_3.jpg

home_3.jpg

1617 ms

home_4.jpg

home_4.jpg

1632 ms

home_5.jpg

home_5.jpg

1639 ms

home_6.jpg

home_6.jpg

1694 ms

home_7.jpg

home_7.jpg

1818 ms

home_8.jpg

home_8.jpg

1942 ms

home_9.jpg

home_9.jpg

1972 ms

home_10.jpg

home_10.jpg

1971 ms

index.php

index.php

4835 ms

a3.gif

a3.gif

2033 ms

1.jpg

1.jpg

2156 ms

i_lo2.gif

i_lo2.gif

7537 ms

mobile.css

mobile.css

19 ms

jquery-1.8.2.min.js

jquery-1.8.2.min.js

21 ms

scroll.js

scroll.js

85 ms

b8.png

b8.png

94 ms

h.js

h.js

742 ms

21.gif

21.gif

742 ms

hm.gif

hm.gif

362 ms

hm.gif

hm.gif

425 ms

Accessibility Review

lh168.net accessibility score

45

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.

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

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.

SEO Factors

lh168.net SEO score

85

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    GBK

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lh168.net can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Lh168.net main page’s claimed encoding is gbk. 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

lh168.net

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