Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

fnp.com

FNP: India's #1 Online Gift Store | Flowers, Cakes, Gift Hampers etc.

Page Load Speed

4.1 sec in total

First Response

443 ms

Resources Loaded

3.1 sec

Page Rendered

557 ms

fnp.com screenshot

About Website

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

FNP India’s largest online gift shop for Flowers, Cakes, Plants, Personalised Gifts & more. We promise ✅ midnight & ✅ same-day delivery in India with FREE shipping!

Visit fnp.com

Key Findings

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

Performance Metrics

fnp.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

26/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value3,830 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.8 s

2/100

10%

Network Requests Diagram

fnp.com

443 ms

www.fnp.com

1307 ms

analytics.js

39 ms

newstylemin.css

19 ms

allCSS1.css

16 ms

Our browser made a total of 133 requests to load all elements on the main page. We found that 6% of them (8 requests) were addressed to the original Fnp.com, 33% (44 requests) were made to D3o2xaj9wtzoci.cloudfront.net and 28% (37 requests) were made to D1lzdxszw6usmj.cloudfront.net. The less responsive or slowest element that took the longest time to load (1.3 sec) belongs to the original domain Fnp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (46%)

Content Size

2.3 MB

After Optimization

1.2 MB

In fact, the total size of Fnp.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 953.2 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 290.1 kB

  • Original 338.4 kB
  • After minification 251.2 kB
  • After compression 48.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. This page needs HTML code to be minified as it can gain 87.2 kB, which is 26% 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 290.1 kB or 86% of the original size.

Image Optimization

-3%

Potential reduce by 27.2 kB

  • Original 953.2 kB
  • After minification 925.9 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. FNP images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 492.1 kB

  • Original 691.6 kB
  • After minification 640.1 kB
  • After compression 199.5 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 492.1 kB or 71% of the original size.

CSS Optimization

-83%

Potential reduce by 229.2 kB

  • Original 275.1 kB
  • After minification 270.9 kB
  • After compression 45.9 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. Fnp.com needs all CSS files to be minified and compressed as it can save up to 229.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 56 (43%)

Requests Now

129

After Optimization

73

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

Accessibility Review

fnp.com accessibility score

79

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

Image elements do not have [alt] attributes

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

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

fnp.com best practices score

67

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

fnp.com SEO score

83

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fnp.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Fnp.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

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