Tools & Wizards About Us
pixiedust.in screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 44

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

pixiedust.in

Pixie Dust | Invitations, Stationery & Lifestyle Design | Mumbai

Page Load Speed

6.4 sec in total

First Response

1 sec

Resources Loaded

5.1 sec

Page Rendered

257 ms

pixiedust.in screenshot

About Website

Visit pixiedust.in now to see the best up-to-date Pixie Dust content and also check out these interesting facts you probably never knew about pixiedust.in

Pixie Dust is a Mumbai-based lifestyle design studio specializing in bespoke invitations & event design. Your one-stop solution to curate the most memorable experience for any special event from invit...

Visit pixiedust.in

Key Findings

We analyzed Pixiedust.in page load time and found that the first response time was 1 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

pixiedust.in performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value15.1 s

0/100

25%

SI (Speed Index)

Value14.5 s

1/100

10%

TBT (Total Blocking Time)

Value190 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value1.029

2/100

15%

TTI (Time to Interactive)

Value13.2 s

12/100

10%

Network Requests Diagram

pixiedust.in

1037 ms

bootstrap.css

271 ms

hamburger.css

470 ms

ezmark.css

477 ms

animate.min.css

488 ms

Our browser made a total of 60 requests to load all elements on the main page. We found that 87% of them (52 requests) were addressed to the original Pixiedust.in, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Connect.facebook.net. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Pixiedust.in.

Page Optimization Overview & Recommendations

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

Content Size

2.1 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pixiedust.in main page is 2.1 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. 60% of websites need less resources to load. Images take 2.0 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 23.0 kB

  • Original 29.2 kB
  • After minification 26.3 kB
  • After compression 6.2 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 23.0 kB or 79% of the original size.

Image Optimization

-28%

Potential reduce by 546.1 kB

  • Original 2.0 MB
  • After minification 1.4 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. Obviously, Pixie Dust needs image optimization as it can save up to 546.1 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-3%

Potential reduce by 3.8 kB

  • Original 113.7 kB
  • After minification 113.7 kB
  • After compression 109.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.

CSS Optimization

-12%

Potential reduce by 4.7 kB

  • Original 40.9 kB
  • After minification 40.6 kB
  • After compression 36.1 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. Pixiedust.in needs all CSS files to be minified and compressed as it can save up to 4.7 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (54%)

Requests Now

54

After Optimization

25

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pixiedust.in

pixiedust.in

1037 ms

bootstrap.css

bootstrap.css

271 ms

hamburger.css

hamburger.css

470 ms

ezmark.css

ezmark.css

477 ms

animate.min.css

animate.min.css

488 ms

mouseparallax.css

mouseparallax.css

484 ms

pongstagr.am.css

pongstagr.am.css

483 ms

owl.carousel.css

owl.carousel.css

500 ms

owl.theme.css

owl.theme.css

710 ms

owl.transitions.css

owl.transitions.css

718 ms

colorbox.css

colorbox.css

729 ms

style.css

style.css

731 ms

mobile.css

mobile.css

730 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

769 ms

bootstrap.min.js

bootstrap.min.js

945 ms

jquery.nicescroll.min.js

jquery.nicescroll.min.js

958 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

971 ms

inview.min.js

inview.min.js

969 ms

jquery.validate.min.js

jquery.validate.min.js

973 ms

jquery.ezmark.min.js

jquery.ezmark.min.js

981 ms

mouse.parallax.js

mouse.parallax.js

1178 ms

instafeed.min.js

instafeed.min.js

1195 ms

owl.carousel.min.js

owl.carousel.min.js

1209 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

1215 ms

jquery.fakecrop.js

jquery.fakecrop.js

1223 ms

jquery.cookie.js

jquery.cookie.js

1224 ms

main.js

main.js

1412 ms

analytics.js

analytics.js

33 ms

fbevents.js

fbevents.js

67 ms

core.js

core.js

115 ms

loader.gif

loader.gif

701 ms

social_icons.png

social_icons.png

716 ms

background.png

background.png

959 ms

home_banner_mobile.png

home_banner_mobile.png

1450 ms

home_banner_tablet.png

home_banner_tablet.png

1630 ms

home_banner_tablet_landscape.png

home_banner_tablet_landscape.png

2072 ms

sky.png

sky.png

932 ms

hill_tree.png

hill_tree.png

1425 ms

ground.png

ground.png

2580 ms

horse.png

horse.png

1196 ms

arrow.png

arrow.png

1439 ms

Home_Logo.png

Home_Logo.png

1662 ms

home.jpg

home.jpg

3358 ms

01-wedding.png

01-wedding.png

1691 ms

arrow_small.png

arrow_small.png

1859 ms

02-papers.png

02-papers.png

1908 ms

03-digital.png

03-digital.png

1934 ms

logo_footer.png

logo_footer.png

2094 ms

icon_fb.png

icon_fb.png

2150 ms

icon_insta.png

icon_insta.png

2174 ms

icon_pin.png

icon_pin.png

2307 ms

xfbml.customerchat.js

xfbml.customerchat.js

64 ms

crimsontext-regular-webfont.woff

crimsontext-regular-webfont.woff

2298 ms

crimsontext-roman-webfont.woff

crimsontext-roman-webfont.woff

2365 ms

collect

collect

55 ms

collect

collect

64 ms

31 ms

js

js

48 ms

Didot-Bold.woff

Didot-Bold.woff

2682 ms

Didot.woff

Didot.woff

2324 ms

Accessibility Review

pixiedust.in accessibility score

44

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

pixiedust.in best practices score

75

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

High

Browser errors were logged to the console

SEO Factors

pixiedust.in SEO score

78

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 Pixiedust.in 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 Pixiedust.in 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

pixiedust.in

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