Report Summary

  • 44

    Performance

    Renders faster than
    62% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    47% of websites

  • 89

    SEO

    Google-friendlier than
    72% of websites

qdql.net

青岛网站建设,网站推广,网络营销--千龙网络

Page Load Speed

28.8 sec in total

First Response

1.4 sec

Resources Loaded

26.9 sec

Page Rendered

497 ms

qdql.net screenshot

About Website

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

网站建设14年,值得信赖。联系电话0532-88628280/15905425390微信同号

Visit qdql.net

Key Findings

We analyzed Qdql.net page load time and found that the first response time was 1.4 sec and then it took 27.4 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 8 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

qdql.net performance score

44

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value13.6 s

2/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

qdql.net

1396 ms

style.css

457 ms

jquery-1.8.2.min.js

2339 ms

slider.js

2250 ms

myJs.js

957 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 90% of them (44 requests) were addressed to the original Qdql.net, 2% (1 request) were made to S11.cnzz.com and 2% (1 request) were made to Oz.cnzz.com. The less responsive or slowest element that took the longest time to load (20.1 sec) belongs to the original domain Qdql.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 127.2 kB (33%)

Content Size

380.0 kB

After Optimization

252.8 kB

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

HTML Optimization

-74%

Potential reduce by 18.4 kB

  • Original 24.8 kB
  • After minification 23.2 kB
  • After compression 6.5 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 18.4 kB or 74% of the original size.

Image Optimization

-3%

Potential reduce by 6.8 kB

  • Original 205.9 kB
  • After minification 199.1 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. Qdql images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 88.5 kB

  • Original 132.6 kB
  • After minification 126.7 kB
  • After compression 44.1 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 88.5 kB or 67% of the original size.

CSS Optimization

-81%

Potential reduce by 13.6 kB

  • Original 16.7 kB
  • After minification 11.6 kB
  • After compression 3.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. Qdql.net needs all CSS files to be minified and compressed as it can save up to 13.6 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

38

After Optimization

33

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

Accessibility Review

qdql.net accessibility score

70

Accessibility Issues

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

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.

Best Practices

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

qdql.net SEO score

89

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

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

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