Report Summary

  • 62

    Performance

    Renders faster than
    77% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

fillyz.com

IIS Windows Server

Page Load Speed

1.7 sec in total

First Response

52 ms

Resources Loaded

1.4 sec

Page Rendered

252 ms

fillyz.com screenshot

About Website

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

Shop Online Salwar Kameez, Churidar Suits, Anarkali Suits, Designer Sarees, Wedding Lehengas. Buy from Wide range of Indian clothing. Express Shipping to USA, UK, France, Australia

Visit fillyz.com

Key Findings

We analyzed Fillyz.com page load time and found that the first response time was 52 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

fillyz.com performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value5.5 s

55/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.5 s

71/100

10%

Network Requests Diagram

fillyz.com

52 ms

www.fillyz.com

674 ms

bootstrap.css

10 ms

stylesheet.css

17 ms

jquery-ui.min.css

8 ms

Our browser made a total of 93 requests to load all elements on the main page. We found that 84% of them (78 requests) were addressed to the original Fillyz.com, 3% (3 requests) were made to Staticxx.facebook.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (674 ms) belongs to the original domain Fillyz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 915.2 kB (22%)

Content Size

4.2 MB

After Optimization

3.2 MB

In fact, the total size of Fillyz.com main page is 4.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 62.8 kB

  • Original 78.2 kB
  • After minification 77.9 kB
  • After compression 15.4 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 62.8 kB or 80% of the original size.

Image Optimization

-1%

Potential reduce by 38.6 kB

  • Original 3.0 MB
  • After minification 3.0 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. Fillyz images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 389.9 kB

  • Original 574.0 kB
  • After minification 573.9 kB
  • After compression 184.1 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 389.9 kB or 68% of the original size.

CSS Optimization

-89%

Potential reduce by 423.9 kB

  • Original 477.3 kB
  • After minification 476.3 kB
  • After compression 53.4 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. Fillyz.com needs all CSS files to be minified and compressed as it can save up to 423.9 kB or 89% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (52%)

Requests Now

86

After Optimization

41

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

Accessibility Review

fillyz.com accessibility score

83

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

[aria-*] attributes do not match their roles

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.

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

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

Browser errors were logged to the console

SEO Factors

fillyz.com SEO score

82

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

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 uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fillyz.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Fillyz.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 Fillyz. 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: