Tools & Wizards About Us
qijax.com screenshot

Report Summary

  • 88

    Performance

    Renders faster than
    90% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

qijax.com

四川德阳鹏瑞医疗有限公司 - 首页

Page Load Speed

2.1 sec in total

First Response

517 ms

Resources Loaded

1.2 sec

Page Rendered

414 ms

qijax.com screenshot

About Website

Welcome to qijax.com homepage info - get ready to check Qijax best content right away, or after learning these important things about qijax.com

四川德阳鹏瑞医疗有限公司qijax.com经营范围含:医疗咨询、健康管理、康复医疗、中医诊疗、医疗美容、口腔医疗、眼科医疗、妇产医疗；医疗器械、医疗设备、医疗用品、医疗耗材、医疗软件、医疗信息化、远程医疗、智慧医疗；医疗保健、营养保健、医疗器械维修、医疗废物处理、医疗设备租赁、医疗投资管理。

Visit qijax.com

Key Findings

We analyzed Qijax.com page load time and found that the first response time was 517 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

qijax.com performance score

88

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

62/100

25%

SI (Speed Index)

Value2.8 s

96/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.8 s

97/100

10%

Network Requests Diagram

qijax.com

517 ms

style.css

27 ms

home.css

30 ms

jquery.js

25 ms

jquery.lazyload.js

28 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 28% of them (10 requests) were addressed to the original Qijax.com, 58% (21 requests) were made to Img.bobojizy.org and 8% (3 requests) were made to Bf3.hntvoss.com. The less responsive or slowest element that took the longest time to load (665 ms) relates to the external source Bf3.hntvoss.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 87.2 kB (4%)

Content Size

2.2 MB

After Optimization

2.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-73%

Potential reduce by 39.6 kB

  • Original 54.6 kB
  • After minification 53.9 kB
  • After compression 14.9 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 39.6 kB or 73% of the original size.

Image Optimization

-2%

Potential reduce by 35.2 kB

  • Original 2.1 MB
  • After minification 2.0 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. Qijax images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 9.8 kB

  • Original 82.1 kB
  • After minification 82.1 kB
  • After compression 72.3 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 9.8 kB or 12% of the original size.

CSS Optimization

-30%

Potential reduce by 2.6 kB

  • Original 8.6 kB
  • After minification 8.6 kB
  • After compression 6.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. Qijax.com needs all CSS files to be minified and compressed as it can save up to 2.6 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 13 (37%)

Requests Now

35

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

qijax.com

qijax.com

517 ms

style.css

style.css

27 ms

home.css

home.css

30 ms

jquery.js

jquery.js

25 ms

jquery.lazyload.js

jquery.lazyload.js

28 ms

jquery.autocomplete.js

jquery.autocomplete.js

41 ms

home.js

home.js

42 ms

jquery.superslide.js

jquery.superslide.js

43 ms

jquery.lazyload.js

jquery.lazyload.js

43 ms

jquery.base.js

jquery.base.js

45 ms

a8863792d2d66d3a1b32ccc213a63301.jpg

a8863792d2d66d3a1b32ccc213a63301.jpg

100 ms

103.jpg

103.jpg

622 ms

103.jpg

103.jpg

665 ms

103.jpg

103.jpg

562 ms

0ba3c19636c3ec02477bb24bf6455fa4.jpg

0ba3c19636c3ec02477bb24bf6455fa4.jpg

114 ms

d5d98ee93b103fc55ac53fd16a6c694f.jpg

d5d98ee93b103fc55ac53fd16a6c694f.jpg

120 ms

1b868f270430e85093b978385a17fde9.jpg

1b868f270430e85093b978385a17fde9.jpg

119 ms

b26886252351bbcb4204f3c36a923610.jpg

b26886252351bbcb4204f3c36a923610.jpg

126 ms

e9c14c57eff4e3c3db3ceb72b70ae1fb.jpg

e9c14c57eff4e3c3db3ceb72b70ae1fb.jpg

129 ms

722de9238603d0d2039e9a43f3215d41.jpg

722de9238603d0d2039e9a43f3215d41.jpg

126 ms

41bae4d2179ae286d373175ec87e28ad.jpg

41bae4d2179ae286d373175ec87e28ad.jpg

143 ms

e020e6d782f8b3240e57c71afca0e2ea.jpg

e020e6d782f8b3240e57c71afca0e2ea.jpg

130 ms

1d16fd40c61f07e389c510213edc3e4c.jpg

1d16fd40c61f07e389c510213edc3e4c.jpg

132 ms

071af63d15c26d39d6f589d6511b979b.jpg

071af63d15c26d39d6f589d6511b979b.jpg

147 ms

230ec5116968da45003a69e5c99f06aa.jpg

230ec5116968da45003a69e5c99f06aa.jpg

144 ms

b1d2295eefee514ad6ca56db192e68f2.jpg

b1d2295eefee514ad6ca56db192e68f2.jpg

144 ms

7e46b47a1cfd3480bebd2e22f2c21acd.jpg

7e46b47a1cfd3480bebd2e22f2c21acd.jpg

141 ms

5d0ffe183bb8814d561a1a74f967b85b.jpg

5d0ffe183bb8814d561a1a74f967b85b.jpg

143 ms

99532d052308a6540d3140ad7e4ee2b7.jpg

99532d052308a6540d3140ad7e4ee2b7.jpg

156 ms

d34c8fe87694802ca135bf464866c803.jpg

d34c8fe87694802ca135bf464866c803.jpg

157 ms

7f64bda041ed2e3ef624afddb51008e3.jpg

7f64bda041ed2e3ef624afddb51008e3.jpg

152 ms

2853a6665a295c77992216bb9e95688f.jpg

2853a6665a295c77992216bb9e95688f.jpg

165 ms

f49b9cad807b88e260ae43afad8c751e.jpg

f49b9cad807b88e260ae43afad8c751e.jpg

159 ms

28912724e8ad9cdc77b0b6a687c4a132.jpg

28912724e8ad9cdc77b0b6a687c4a132.jpg

163 ms

matomo.js

matomo.js

19 ms

matomo.php

matomo.php

502 ms

Accessibility Review

qijax.com accessibility score

58

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.

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

Definition list items are not wrapped in <dl> elements

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

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

qijax.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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

qijax.com SEO score

82

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

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

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Qijax.com 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 Qijax.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

qijax.com

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