Access nikkiflower.com. Online Flowers, Cakes & Gifts Delivery Across India | NikkiFlower

nikkiflower.com screenshot

8

Performance

Renders faster than
22% of other websites
64

Accessibility

Visual factors better than
that of 29% of websites
58

Best Practices

More advanced features
available than in
20% of websites
92

SEO

Google-friendlier than
74% of websites

First Response

404 ms

Resources Loaded

6.7 sec

Page Rendered

694 ms

nikkiflower.com screenshot

About Website

Click here to check amazing Nikki Flower content for India. Otherwise, check out these important facts you probably never knew about nikkiflower.com

Buy Flowers, Gifts & Cakes online and send to India via NikkiFlower - India's fastest growing online florist. ✓Delivery in 3 hours ✓FREE shipping Order now!

Visit nikkiflower.com

Key Findings

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

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

2/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value2,170 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.366

29/100

15%

TTI (Time to Interactive)

Value17.5 s

4/100

10%

nikkiflower.com

404 ms

www.nikkiflower.com

1026 ms

css

38 ms

material-design-iconic-font.css

773 ms

animate.css

785 ms

Our browser made a total of 193 requests to load all elements on the main page. We found that 94% of them (181 requests) were addressed to the original Nikkiflower.com, 2% (4 requests) were made to Fonts.gstatic.com and 1% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Nikkiflower.com.

Content Size

2.3 MB

After Optimization

2.0 MB

In fact, the total size of Nikkiflower.com main page is 2.3 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. 70% of websites need less resources to load. Images take 1.9 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 184.5 kB

Original 202.4 kB
After minification 110.2 kB
After compression 17.9 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 92.2 kB, which is 46% 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 184.5 kB or 91% of the original size.

Image Optimization

-2%

Potential reduce by 46.6 kB

Original 1.9 MB
After minification 1.8 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. Nikki Flower images are well optimized though.

JavaScript Optimization

-11%

Potential reduce by 10.8 kB

Original 101.1 kB
After minification 101.1 kB
After compression 90.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 10.8 kB or 11% of the original size.

CSS Optimization

-14%

Potential reduce by 11.7 kB

Original 84.4 kB
After minification 84.4 kB
After compression 72.7 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. Nikkiflower.com needs all CSS files to be minified and compressed as it can save up to 11.7 kB or 14% of the original size.

Requests Now

100

After Optimization

81

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

Accessibility Issues

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.

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

ARIA IDs are not unique

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.

High

Buttons do not have an accessible name

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

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

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Links are not crawlable

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/).

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 Nikkiflower.com 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 Nikkiflower.com 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

nikkiflower.com

Open Graph data is detected on the main page of Nikki Flower. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: