Tools & Wizards About Us
18q.net screenshot

Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 38

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

18q.net

广州微信小程序开发定制公司

Page Load Speed

8.1 sec in total

First Response

964 ms

Resources Loaded

6.5 sec

Page Rendered

585 ms

18q.net screenshot

About Website

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

广州科盾网络：新一代智能自助成微信小程序生成系统，易学易懂，功能强大，拥有数千套精美小程序模板，微信小程序开发，1分钟上手，5分钟制作，快速生成微信小程序

Visit 18q.net

Key Findings

We analyzed 18q.net page load time and found that the first response time was 964 ms and then it took 7.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

18q.net performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

77/100

25%

SI (Speed Index)

Value6.3 s

41/100

10%

TBT (Total Blocking Time)

Value290 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.158

73/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

18q.net

964 ms

shangqiao.js

438 ms

common.css

452 ms

style.css

675 ms

jquery-1.11.3.min.js

1106 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 94% of them (58 requests) were addressed to the original 18q.net, 3% (2 requests) were made to Hm.baidu.com and 2% (1 request) were made to Goutong.baidu.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain 18q.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 72.4 kB (5%)

Content Size

1.4 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 23.2 kB

  • Original 29.8 kB
  • After minification 22.9 kB
  • After compression 6.6 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.0 kB, which is 23% 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 23.2 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 30.9 kB

  • Original 1.2 MB
  • After minification 1.2 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. 18 Q images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 14.3 kB

  • Original 203.0 kB
  • After minification 202.4 kB
  • After compression 188.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-36%

Potential reduce by 4.0 kB

  • Original 11.0 kB
  • After minification 11.0 kB
  • After compression 7.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. 18q.net needs all CSS files to be minified and compressed as it can save up to 4.0 kB or 36% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (20%)

Requests Now

61

After Optimization

49

  • AJAX
  • Images
  • JavaScript
  • CSS

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

18q.net

18q.net

964 ms

shangqiao.js

shangqiao.js

438 ms

common.css

common.css

452 ms

style.css

style.css

675 ms

jquery-1.11.3.min.js

jquery-1.11.3.min.js

1106 ms

comm.js

comm.js

441 ms

jquery.SuperSlide.2.1.1.js

jquery.SuperSlide.2.1.1.js

453 ms

uaredirect.js

uaredirect.js

658 ms

hm.js

hm.js

1390 ms

jzxcx-1.jpg

jzxcx-1.jpg

2205 ms

jzxcx-logo.png

jzxcx-logo.png

225 ms

jzxcx-12.jpg

jzxcx-12.jpg

904 ms

jzxcx-2.png

jzxcx-2.png

224 ms

jzxcx-3.png

jzxcx-3.png

223 ms

jzxcx-4.png

jzxcx-4.png

220 ms

jzxcx-13.jpg

jzxcx-13.jpg

1078 ms

jzxcx-14.png

jzxcx-14.png

443 ms

jzxcx-23.png

jzxcx-23.png

444 ms

jzxcx-24.png

jzxcx-24.png

665 ms

jzxcx-25.png

jzxcx-25.png

663 ms

jzxcx-26.png

jzxcx-26.png

664 ms

jzxcx-37.jpg

jzxcx-37.jpg

1098 ms

jzxcx-38.jpg

jzxcx-38.jpg

893 ms

jzxcx-39.jpg

jzxcx-39.jpg

1110 ms

jzxcx-40.jpg

jzxcx-40.jpg

1116 ms

jzxcx-41.jpg

jzxcx-41.jpg

1131 ms

jzxcx-15.png

jzxcx-15.png

1294 ms

jzxcx-16.png

jzxcx-16.png

1317 ms

jzxcx-17.png

jzxcx-17.png

1333 ms

jzxcx-18.png

jzxcx-18.png

1336 ms

jzxcx-19.png

jzxcx-19.png

1356 ms

jzxcx-20.png

jzxcx-20.png

1509 ms

jzxcx-21.png

jzxcx-21.png

1536 ms

jzxcx-22.png

jzxcx-22.png

1554 ms

jzxcx-6.png

jzxcx-6.png

1556 ms

jzxcx-7.png

jzxcx-7.png

1581 ms

jzxcx-8.png

jzxcx-8.png

1725 ms

jzxcx-9.png

jzxcx-9.png

1754 ms

jzxcx-53.jpg

jzxcx-53.jpg

1776 ms

qq.png

qq.png

1775 ms

jzxcx-27.png

jzxcx-27.png

1733 ms

jzxcx-10.jpg

jzxcx-10.jpg

1875 ms

jzxcx-11.jpg

jzxcx-11.jpg

1903 ms

jzxcx-101.jpg

jzxcx-101.jpg

1926 ms

jzxcx-102.jpg

jzxcx-102.jpg

1930 ms

list.asp

list.asp

2154 ms

jzxcx-103.jpg

jzxcx-103.jpg

1953 ms

nes_19.gif

nes_19.gif

1978 ms

jzxcx-50.png

jzxcx-50.png

2001 ms

jzxcx-52.png

jzxcx-52.png

1790 ms

jzxcx-54.png

jzxcx-54.png

1949 ms

jzxcx-56.png

jzxcx-56.png

1757 ms

jzxcx-58.png

jzxcx-58.png

1760 ms

jzxcx-60.png

jzxcx-60.png

1780 ms

hm.gif

hm.gif

305 ms

b.js

b.js

1831 ms

jzxcx-103.png

jzxcx-103.png

1560 ms

jzxcx-106.jpg

jzxcx-106.jpg

1695 ms

20183301585937876.jpg

20183301585937876.jpg

239 ms

20183301592733344.png

20183301592733344.png

265 ms

jzxcx-mob.png

jzxcx-mob.png

270 ms

affim.js

affim.js

2092 ms

Accessibility Review

18q.net accessibility score

38

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

Form elements do not have associated labels

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

18q.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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

18q.net SEO score

69

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

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

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 18q.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 18q.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

18q.net

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