Tools & Wizards About Us
21942.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

21942.com

51408诸葛亮主页|诸葛亮玄机2站|马会开奖结果|马会特供资料站|马会玄机|马会开奖记录|香港挂牌|赛马会

Page Load Speed

20.8 sec in total

First Response

7.4 sec

Resources Loaded

10.4 sec

Page Rendered

3 sec

21942.com screenshot

About Website

Visit 21942.com now to see the best up-to-date 21942 content and also check out these interesting facts you probably never knew about 21942.com

51408诸葛亮主页|诸葛亮玄机2站|马会开奖结果|马会特供资料站|马会玄机|马会开奖记录|香港挂牌|赛马会

Visit 21942.com

Key Findings

We analyzed 21942.com page load time and found that the first response time was 7.4 sec and then it took 13.4 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

21942.com performance score

0

Network Requests Diagram

lipitor-lawsuit.org

7377 ms

reset.css

148 ms

defaults.css

149 ms

style.css

152 ms

style.css

145 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original 21942.com, 3% (2 requests) were made to Apis.google.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (7.4 sec) relates to the external source Lipitor-lawsuit.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 443.4 kB (37%)

Content Size

1.2 MB

After Optimization

764.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 21942.com main page is 1.2 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. 50% of websites need less resources to load. Images take 760.0 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 88.2 kB

  • Original 119.6 kB
  • After minification 116.3 kB
  • After compression 31.4 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 88.2 kB or 74% of the original size.

Image Optimization

-19%

Potential reduce by 142.1 kB

  • Original 760.0 kB
  • After minification 617.9 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, 21942 needs image optimization as it can save up to 142.1 kB or 19% 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 152.0 kB

  • Original 230.4 kB
  • After minification 225.6 kB
  • After compression 78.4 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 152.0 kB or 66% of the original size.

CSS Optimization

-62%

Potential reduce by 61.0 kB

  • Original 98.1 kB
  • After minification 81.3 kB
  • After compression 37.1 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. 21942.com needs all CSS files to be minified and compressed as it can save up to 61.0 kB or 62% of the original size.

Requests Breakdown

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

Requests Now

66

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lipitor-lawsuit.org

lipitor-lawsuit.org

7377 ms

reset.css

reset.css

148 ms

defaults.css

defaults.css

149 ms

style.css

style.css

152 ms

style.css

style.css

145 ms

dashicons.min.css

dashicons.min.css

262 ms

desktop_style.css

desktop_style.css

153 ms

styles.css

styles.css

242 ms

form_style.css

form_style.css

253 ms

fbookmarks.css

fbookmarks.css

234 ms

jquery.js

jquery.js

305 ms

jquery-migrate.min.js

jquery-migrate.min.js

269 ms

front_end_script.js

front_end_script.js

300 ms

cntctfrm.js

cntctfrm.js

319 ms

jquery.fbookmarks.js

jquery.fbookmarks.js

322 ms

plusone.js

plusone.js

66 ms

superfish.js

superfish.js

354 ms

jquery.mobilemenu.js

jquery.mobilemenu.js

364 ms

external-tracking.min.js

external-tracking.min.js

362 ms

jscripts.php

jscripts.php

414 ms

widgets.js

widgets.js

5 ms

jquery.form.min.js

jquery.form.min.js

332 ms

scripts.js

scripts.js

334 ms

hoverIntent.min.js

hoverIntent.min.js

444 ms

jscripts-ftr-min.js

jscripts-ftr-min.js

443 ms

wp-embed.min.js

wp-embed.min.js

449 ms

css

css

53 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

343 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

4 ms

analytics.js

analytics.js

6 ms

collect

collect

15 ms

diaglines.png

diaglines.png

1146 ms

lipitor-lawsuit.jpg

lipitor-lawsuit.jpg

1148 ms

date.png

date.png

1144 ms

category.png

category.png

1142 ms

lipitor-lawsuit.jpg

lipitor-lawsuit.jpg

1146 ms

lipitor-type-II-diabetes-300x191.jpg

lipitor-type-II-diabetes-300x191.jpg

1145 ms

lipitor-lawsuit-lipitor-settlement-300x200.jpg

lipitor-lawsuit-lipitor-settlement-300x200.jpg

1148 ms

LIPITOR-lawyer-150x150.jpg

LIPITOR-lawyer-150x150.jpg

1151 ms

Dollarphotoclub_41127084-150x150.jpg

Dollarphotoclub_41127084-150x150.jpg

1147 ms

lipitor-lawsuit1-150x150.jpg

lipitor-lawsuit1-150x150.jpg

1147 ms

richard-m-gergel-lipitor-mdl-150x150.jpg

richard-m-gergel-lipitor-mdl-150x150.jpg

1149 ms

Lipitor-multidistrict-litigation.jpg

Lipitor-multidistrict-litigation.jpg

1149 ms

lipitor-settlement-lipitor-claims-199x300.jpg

lipitor-settlement-lipitor-claims-199x300.jpg

1151 ms

lipitor-lawsuit-sue-pfizer-300x300.jpg

lipitor-lawsuit-sue-pfizer-300x300.jpg

1151 ms

content-300x300.jpg

content-300x300.jpg

1152 ms

lipitor-news-lipitor-lawsuit-300x200.jpg

lipitor-news-lipitor-lawsuit-300x200.jpg

1155 ms

Lipitor-Lawsuit-Lipitor-Claim-300x199.jpg

Lipitor-Lawsuit-Lipitor-Claim-300x199.jpg

1152 ms

lipitor-lawsuit-diabetes-2-300x199.jpg

lipitor-lawsuit-diabetes-2-300x199.jpg

1157 ms

lipitor-settlement-lawsuit-3-291x300.jpg

lipitor-settlement-lawsuit-3-291x300.jpg

1154 ms

lipitor-settlement-diabetes-lawsuit-300x200.jpg

lipitor-settlement-diabetes-lawsuit-300x200.jpg

1152 ms

lipitor-settlement-200x300.jpg

lipitor-settlement-200x300.jpg

1157 ms

lipitor-claims-lawsuit1-300x106.jpg

lipitor-claims-lawsuit1-300x106.jpg

1154 ms

lipitor-causes-type-II-diabetes-300x199.jpg

lipitor-causes-type-II-diabetes-300x199.jpg

1154 ms

lipitor-lawsuit-diabetes-300x199.jpg

lipitor-lawsuit-diabetes-300x199.jpg

1160 ms

Dollarphotoclub_41127084-216x300.jpg

Dollarphotoclub_41127084-216x300.jpg

1166 ms

lipitor-side-effects-257x300.jpeg

lipitor-side-effects-257x300.jpeg

1157 ms

lawsuit-image-300x294.jpg

lawsuit-image-300x294.jpg

1157 ms

lipitorlawsuitsettlement.jpg

lipitorlawsuitsettlement.jpg

1157 ms

nurse-talking-about-diabetes-300x199.jpg

nurse-talking-about-diabetes-300x199.jpg

1167 ms

diabetes.jpg

diabetes.jpg

1167 ms

Lipitor-Causing-Diabetes-in-Women-300x204.jpg

Lipitor-Causing-Diabetes-in-Women-300x204.jpg

1168 ms

search.png

search.png

1110 ms

widget-list.png

widget-list.png

1107 ms

ajax-loader.gif

ajax-loader.gif

1063 ms

like.php

like.php

183 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

28 ms

SEO Factors

21942.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 21942.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that 21942.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

21942.com

Open Graph data is detected on the main page of 21942. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: