Report Summary

  • 64

    Performance

    Renders faster than
    77% of other websites

  • 49

    Accessibility

    Visual factors better than
    that of 20% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

prettyflowers.xyz

永乐国际凯发_凯发悦公馆_凯发ag旗舰厅登录-昌吉市永乐国际凯发网络科技公司欢迎您

Page Load Speed

2.3 sec in total

First Response

144 ms

Resources Loaded

1.7 sec

Page Rendered

447 ms

About Website

Visit prettyflowers.xyz now to see the best up-to-date Prettyflowers content and also check out these interesting facts you probably never knew about prettyflowers.xyz

k8手机登录全站登录虹乐教育永乐国际凯发成立于2019年05月17日,注册地位于中国(k8手机登录全站登录)自由贸易凯发ag旗舰厅登录临港新24k88体育app宏祥凯发app官方网站83弄1-42号20幢118室,法定代表人为戴缨。经营范围包括从事教育24K88官网领域内的技术开发、技术咨询、技术服务、技术转让,市场营销策划,文化艺术交流活动策划,会议及展览服务,网页设计,办公用品、纸制品、工艺品...

Visit prettyflowers.xyz

Key Findings

We analyzed Prettyflowers.xyz page load time and found that the first response time was 144 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

prettyflowers.xyz performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value3.9 s

82/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.9 s

77/100

10%

Network Requests Diagram

www.prettyflowers.xyz

144 ms

jquery-3.5.103.min.js

28 ms

GFoZ1sd_Ot1JrTVNaX7mUyg1GUqO03nJIb2ggjInY_mC1D69heNZxA==.css

10 ms

FQ3XYpYL-AE=.css

202 ms

matomo.js

200 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 89% of them (24 requests) were addressed to the original Prettyflowers.xyz, 7% (2 requests) were made to 1etu.com and 4% (1 request) were made to Cdn.3ae.jp. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Prettyflowers.xyz.

Page Optimization Overview & Recommendations

Page size can be reduced by 38.3 kB (49%)

Content Size

77.8 kB

After Optimization

39.5 kB

In fact, the total size of Prettyflowers.xyz main page is 77.8 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. HTML takes 50.6 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 35.5 kB

  • Original 50.6 kB
  • After minification 45.9 kB
  • After compression 15.2 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 35.5 kB or 70% of the original size.

JavaScript Optimization

-10%

Potential reduce by 2.9 kB

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

Requests Breakdown

We found no issues to fix!

Requests Now

26

After Optimization

26

The browser has sent 26 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Prettyflowers. According to our analytics all requests are already optimized.

Accessibility Review

prettyflowers.xyz accessibility score

49

Accessibility Issues

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

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

prettyflowers.xyz best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

prettyflowers.xyz SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prettyflowers.xyz can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that Prettyflowers.xyz 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 Prettyflowers. 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: