Tools & Wizards About Us
blue.boutique screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% 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

  • 88

    SEO

    Google-friendlier than
    65% of websites

blue.boutique

BLUE

Page Load Speed

2 sec in total

First Response

50 ms

Resources Loaded

1.5 sec

Page Rendered

387 ms

blue.boutique screenshot

About Website

Click here to check amazing BLUE content. Otherwise, check out these important facts you probably never knew about blue.boutique

Blue, locally owned women's clothing boutique offering boho chic and athleisure apparel from sustainable fashion and lifestyle brands

Visit blue.boutique

Key Findings

We analyzed Blue.boutique page load time and found that the first response time was 50 ms and then it took 1.9 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

blue.boutique performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value8.9 s

1/100

25%

SI (Speed Index)

Value6.2 s

43/100

10%

TBT (Total Blocking Time)

Value390 ms

69/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

blue.boutique

50 ms

rs=w:1920,m

566 ms

script.js

125 ms

UX.4.43.8.js

26 ms

script.js

92 ms

Our browser made a total of 26 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Blue.boutique, 92% (24 requests) were made to Img1.wsimg.com and 4% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Img1.wsimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 322.7 kB (16%)

Content Size

2.0 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-86%

Potential reduce by 140.5 kB

  • Original 163.9 kB
  • After minification 163.9 kB
  • After compression 23.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 140.5 kB or 86% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-56%

Potential reduce by 182.2 kB

  • Original 324.3 kB
  • After minification 324.3 kB
  • After compression 142.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 182.2 kB or 56% of the original size.

Requests Breakdown

Number of requests can be reduced by 4 (16%)

Requests Now

25

After Optimization

21

  • Images
  • JavaScript

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

Network Requests Diagram

blue.boutique

blue.boutique

50 ms

rs=w:1920,m

rs=w:1920,m

566 ms

script.js

script.js

125 ms

UX.4.43.8.js

UX.4.43.8.js

26 ms

script.js

script.js

92 ms

js

js

49 ms

rs=w:1920,m

rs=w:1920,m

606 ms

rs=w:370,cg:true

rs=w:370,cg:true

325 ms

rs=w:370,cg:true

rs=w:370,cg:true

489 ms

rs=w:370,h:370,cg:true

rs=w:370,h:370,cg:true

446 ms

rs=w:370,cg:true

rs=w:370,cg:true

539 ms

rs=w:370,cg:true,m

rs=w:370,cg:true,m

747 ms

rs=w:370,cg:true

rs=w:370,cg:true

566 ms

rs=w:370,cg:true,m

rs=w:370,cg:true,m

822 ms

rs=w:370,cg:true

rs=w:370,cg:true

614 ms

rs=w:370,cg:true

rs=w:370,cg:true

1138 ms

rs=w:370,h:493.3333333333333,cg:true

rs=w:370,h:493.3333333333333,cg:true

784 ms

rs=w:370,cg:true

rs=w:370,cg:true

694 ms

rs=w:370,cg:true,m

rs=w:370,cg:true,m

892 ms

rs=w:370,h:278.1954887218045,cg:true

rs=w:370,h:278.1954887218045,cg:true

1466 ms

rs=w:370,cg:true,m

rs=w:370,cg:true,m

1364 ms

rs=w:370,cg:true

rs=w:370,cg:true

872 ms

rs=w:370,cg:true,m

rs=w:370,cg:true,m

1294 ms

rs=w:370,cg:true,m

rs=w:370,cg:true,m

1152 ms

rs=w:370,h:370,cg:true

rs=w:370,h:370,cg:true

1386 ms

scc-c2.min.js

scc-c2.min.js

1129 ms

Accessibility Review

blue.boutique 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.

High

[aria-hidden="true"] elements contain focusable descendents

High

[aria-*] attributes do not have valid values

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

Image elements do not have [alt] attributes

Best Practices

blue.boutique 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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

blue.boutique SEO score

88

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

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Blue.boutique 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 Blue.boutique 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

blue.boutique

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