Tools & Wizards About Us
floragora.kiwi screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

floragora.kiwi

Swap flowers | Sell flowers | Buy flowers - in New Zealand

Page Load Speed

1.1 sec in total

First Response

34 ms

Resources Loaded

727 ms

Page Rendered

346 ms

floragora.kiwi screenshot

About Website

Welcome to floragora.kiwi homepage info - get ready to check Floragora best content right away, or after learning these important things about floragora.kiwi

Floragora.kiwi in an online marketplace for swapping, selling and buying flowers in New Zealand. It's free to get started.

Visit floragora.kiwi

Key Findings

We analyzed Floragora.kiwi page load time and found that the first response time was 34 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

floragora.kiwi performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

45/100

25%

SI (Speed Index)

Value4.0 s

81/100

10%

TBT (Total Blocking Time)

Value450 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0.026

100/100

15%

TTI (Time to Interactive)

Value6.6 s

57/100

10%

Network Requests Diagram

floragora.kiwi

34 ms

my.floragora.com

58 ms

www.floragora.com

89 ms

analytics.js

27 ms

gtm.js

112 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Floragora.kiwi, 30% (7 requests) were made to Fonts.gstatic.com and 22% (5 requests) were made to Scripts.swipepages.com. The less responsive or slowest element that took the longest time to load (546 ms) relates to the external source Floragora.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 234.7 kB (27%)

Content Size

867.3 kB

After Optimization

632.6 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Floragora.kiwi main page is 867.3 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. 50% of websites need less resources to load. Images take 744.3 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 80.6 kB

  • Original 102.0 kB
  • After minification 101.1 kB
  • After compression 21.3 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 80.6 kB or 79% of the original size.

Image Optimization

-21%

Potential reduce by 154.0 kB

  • Original 744.3 kB
  • After minification 590.3 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. Obviously, Floragora needs image optimization as it can save up to 154.0 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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

Number of requests can be reduced by 8 (62%)

Requests Now

13

After Optimization

5

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 13 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Floragora. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 9 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

floragora.kiwi

floragora.kiwi

34 ms

my.floragora.com

my.floragora.com

58 ms

www.floragora.com

www.floragora.com

89 ms

analytics.js

analytics.js

27 ms

gtm.js

gtm.js

112 ms

css

css

97 ms

floragora-logo-new-02-750.png

floragora-logo-new-02-750.png

182 ms

jquery.min.js

jquery.min.js

162 ms

asyncloader.min.js

asyncloader.min.js

178 ms

helpers.min.js

helpers.min.js

177 ms

sp-events.js

sp-events.js

546 ms

tatsu.min.js

tatsu.min.js

176 ms

analytics.min.js

analytics.min.js

184 ms

collect

collect

77 ms

magic-pattern-design-blob-3.png

magic-pattern-design-blob-3.png

153 ms

zYXgKVElMYYaJe8bpLHnCwDKhdHeEw.woff

zYXgKVElMYYaJe8bpLHnCwDKhdHeEw.woff

143 ms

zYX9KVElMYYaJe8bpLHnCwDKjSL9AIFscg.woff

zYX9KVElMYYaJe8bpLHnCwDKjSL9AIFscg.woff

144 ms

zYX9KVElMYYaJe8bpLHnCwDKjQ76AIFscg.woff

zYX9KVElMYYaJe8bpLHnCwDKjQ76AIFscg.woff

144 ms

js

js

99 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTQ3iQ.woff

XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmdTQ3iQ.woff

47 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3iQ.woff

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmdTQ3iQ.woff

68 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDIkhdTQ3iQ.woff

XRXI3I6Li01BKofiOc5wtlZ2di8HDIkhdTQ3iQ.woff

68 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3iQ.woff

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshdTQ3iQ.woff

69 ms

Accessibility Review

floragora.kiwi accessibility score

78

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

button, link, and menuitem elements do not have accessible names.

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

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

floragora.kiwi best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

floragora.kiwi SEO score

75

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

floragora.kiwi

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