Report Summary

  • 81

    Performance

    Renders faster than
    87% of other websites

  • 43

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 62

    SEO

    Google-friendlier than
    22% of websites

wjflower.com

四川省花卉协会-四川省花协-省花协-四川花木网上花木市场,四川园林绿化苗木价格,苗木求购信息

Page Load Speed

11 sec in total

First Response

5 sec

Resources Loaded

5.8 sec

Page Rendered

225 ms

wjflower.com screenshot

About Website

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

四川省花花协会平台是,网站提供四川花卉苗木行业网络宣传、绿化苗木价格、苗木求购信息、园林资讯、园林绿化工程招投标、园林苗木交流等,花木信息天天更新。

Visit wjflower.com

Key Findings

We analyzed Wjflower.com page load time and found that the first response time was 5 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

wjflower.com performance score

81

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

70/100

25%

SI (Speed Index)

Value6.4 s

41/100

10%

TBT (Total Blocking Time)

Value170 ms

92/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value3.7 s

90/100

10%

Network Requests Diagram

wjflower.com

5008 ms

125.65.109.21

769 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that 50% of them (1 request) were addressed to the original Wjflower.com, 50% (1 request) were made to 0. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain Wjflower.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 56 B (27%)

Content Size

211 B

After Optimization

155 B

In fact, the total size of Wjflower.com main page is 211 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 211 B which makes up the majority of the site volume.

HTML Optimization

-27%

Potential reduce by 56 B

  • Original 211 B
  • After minification 210 B
  • After compression 155 B

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 56 B or 27% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

wjflower.com accessibility score

43

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.

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

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

wjflower.com best practices score

50

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

High

Browser errors were logged to the console

SEO Factors

wjflower.com SEO score

62

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

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    N/A

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