Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 99

    Accessibility

    Visual factors better than
    that of 96% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

peachesandtheboy.com

Kids Shop | Peaches and the boy- The Coolest Kids Brands | Cyprus

Page Load Speed

3.1 sec in total

First Response

67 ms

Resources Loaded

2.9 sec

Page Rendered

71 ms

About Website

Click here to check amazing Peaches And The Boy content. Otherwise, check out these important facts you probably never knew about peachesandtheboy.com

Peaches and the boy, a kids clothing store with the coolest kids brands. Exciting and super fun designs and brands in kidswear with focus on quality and ethically made materials.

Visit peachesandtheboy.com

Key Findings

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

Performance Metrics

peachesandtheboy.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value5,350 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value18.1 s

3/100

10%

Network Requests Diagram

www.peachesandtheboy.com

67 ms

originTrials.41d7301a.bundle.min.js

37 ms

minified.js

44 ms

focus-within-polyfill.js

42 ms

polyfill.min.js

448 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Peachesandtheboy.com, 58% (42 requests) were made to Static.wixstatic.com and 19% (14 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (66%)

Content Size

1.7 MB

After Optimization

581.3 kB

In fact, the total size of Peachesandtheboy.com main page is 1.7 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. 45% of websites need less resources to load. HTML takes 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 1.0 MB

  • Original 1.2 MB
  • After minification 1.2 MB
  • After compression 220.1 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 1.0 MB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 139.3 kB
  • After minification 139.3 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. Peaches And The Boy images are well optimized though.

JavaScript Optimization

-30%

Potential reduce by 97.2 kB

  • Original 319.2 kB
  • After minification 319.1 kB
  • After compression 222.0 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 97.2 kB or 30% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (19%)

Requests Now

58

After Optimization

47

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

Accessibility Review

peachesandtheboy.com accessibility score

99

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

Best Practices

peachesandtheboy.com best practices score

92

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

Page has valid source maps

SEO Factors

peachesandtheboy.com SEO score

97

Search Engine Optimization Advices

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 Peachesandtheboy.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 Peachesandtheboy.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 data is detected on the main page of Peaches And The Boy. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: