Report Summary

  • 87

    Performance

    Renders faster than
    90% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

prettyflowers.xyz

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

Page Load Speed

966 ms in total

First Response

357 ms

Resources Loaded

491 ms

Page Rendered

118 ms

prettyflowers.xyz screenshot

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 357 ms and then it took 609 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

prettyflowers.xyz performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.0 s

100/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value290 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.202

61/100

15%

TTI (Time to Interactive)

Value3.2 s

94/100

10%

Network Requests Diagram

prettyflowers.xyz

357 ms

caf.js

28 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 Prettyflowers.xyz, 50% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (357 ms) belongs to the original domain Prettyflowers.xyz.

Page Optimization Overview & Recommendations

Page size can be reduced by 25.8 kB (30%)

Content Size

86.2 kB

After Optimization

60.4 kB

In fact, the total size of Prettyflowers.xyz main page is 86.2 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Javascripts take 52.5 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 25.7 kB

  • Original 33.8 kB
  • After minification 33.4 kB
  • After compression 8.1 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 25.7 kB or 76% of the original size.

JavaScript Optimization

-0%

Potential reduce by 123 B

  • Original 52.5 kB
  • After minification 52.5 kB
  • After compression 52.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

1

After Optimization

1

The browser has sent 1 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

63

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.

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

<frame> or <iframe> elements do not have a title

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

General

Impact

Issue

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

prettyflowers.xyz SEO score

83

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

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 doesn't use legible font sizes

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: