Report Summary

  • 81

    Performance

    Renders faster than
    87% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 46

    SEO

    Google-friendlier than
    18% of websites

jhrl.net

金华妇科医院_金华人流医院_金华专业女性医院_金华妇科哪家好_金华盛兴医院

Page Load Speed

60.8 sec in total

First Response

2.4 sec

Resources Loaded

58.1 sec

Page Rendered

321 ms

jhrl.net screenshot

About Website

Welcome to jhrl.net homepage info - get ready to check Jhrl best content right away, or after learning these important things about jhrl.net

金华无痛人流多少钱、金华人流哪里好,一直是人们关注的焦点,金华无痛人流医院提供专业人工流产、无痛人流、无痛微管人流、超导可视无痛人流、双腔减压无痛人流等技术介绍,是您了解人流前后保健知识的较佳网站,金华专业人流医院!!。

Visit jhrl.net

Key Findings

We analyzed Jhrl.net page load time and found that the first response time was 2.4 sec and then it took 58.4 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 14 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

jhrl.net performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

55/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value160 ms

94/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.8 s

97/100

10%

Network Requests Diagram

jhrl.net

2415 ms

www.jhrl.net

14887 ms

head.css

1089 ms

style.css

1811 ms

foot.css

719 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 71% of them (76 requests) were addressed to the original Jhrl.net, 12% (13 requests) were made to Nk.jhtj.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 Jhrl.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 141.3 kB (53%)

Content Size

264.7 kB

After Optimization

123.4 kB

In fact, the total size of Jhrl.net main page is 264.7 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. 15% of websites need less resources to load. Javascripts take 125.0 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 44.9 kB

  • Original 56.1 kB
  • After minification 50.3 kB
  • After compression 11.3 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 44.9 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 1.6 kB

  • Original 65.8 kB
  • After minification 64.2 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. Jhrl images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 80.7 kB

  • Original 125.0 kB
  • After minification 123.6 kB
  • After compression 44.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 80.7 kB or 65% of the original size.

CSS Optimization

-80%

Potential reduce by 14.2 kB

  • Original 17.8 kB
  • After minification 15.2 kB
  • After compression 3.6 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. Jhrl.net needs all CSS files to be minified and compressed as it can save up to 14.2 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 67 (75%)

Requests Now

89

After Optimization

22

The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Jhrl. 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 from 5 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

jhrl.net accessibility score

57

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

jhrl.net 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

SEO Factors

jhrl.net SEO score

46

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

High

robots.txt is not valid

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

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jhrl.net 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 Jhrl.net main page’s claimed encoding is gb2312. 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

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