Tools & Wizards About Us
frugi.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

frugi.com

Organic Baby Clothes | Organic Kids Clothes | Frugi

Page Load Speed

1.7 sec in total

First Response

20 ms

Resources Loaded

1.5 sec

Page Rendered

190 ms

frugi.com screenshot

About Website

Click here to check amazing Frugi content. Otherwise, check out these important facts you probably never knew about frugi.com

Frugi organic clothing; from new-born babies to girls and boys up to 10 years and women's breastfeeding wear for mums everywhere. Shop online.

Visit frugi.com

Key Findings

We analyzed Frugi.com page load time and found that the first response time was 20 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 35% of websites can load faster.

Performance Metrics

frugi.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value1,790 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.0 s

5/100

10%

Network Requests Diagram

frugi.com

20 ms

www.welovefrugi.com

694 ms

1395

117 ms

common

63 ms

layout

53 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Frugi.com, 37% (23 requests) were made to Welovefrugi.com and 27% (17 requests) were made to Img.welovefrugi.com. The less responsive or slowest element that took the longest time to load (694 ms) relates to the external source Welovefrugi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 115.4 kB (5%)

Content Size

2.5 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Frugi.com main page is 2.5 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. 55% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 115.4 kB

  • Original 132.9 kB
  • After minification 96.0 kB
  • After compression 17.5 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 36.9 kB, which is 28% 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 115.4 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-0%

Potential reduce by 57 B

  • Original 127.1 kB
  • After minification 127.1 kB
  • After compression 127.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 20 B

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.

Requests Breakdown

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

Requests Now

58

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

frugi.com

frugi.com

20 ms

www.welovefrugi.com

www.welovefrugi.com

694 ms

1395

1395

117 ms

common

common

63 ms

layout

layout

53 ms

standard

standard

60 ms

custom-css

custom-css

56 ms

css

css

77 ms

gpp6byo.css

gpp6byo.css

72 ms

JavaScriptResourceHandler.axd

JavaScriptResourceHandler.axd

368 ms

graphenehc.js

graphenehc.js

362 ms

tp.widget.bootstrap.min.js

tp.widget.bootstrap.min.js

68 ms

otSDKStub.js

otSDKStub.js

90 ms

swiper-bundle.min.css

swiper-bundle.min.css

72 ms

swiper-bundle.min.js

swiper-bundle.min.js

93 ms

p.css

p.css

43 ms

p.css

p.css

46 ms

p.css

p.css

44 ms

p.css

p.css

26 ms

jquery

jquery

19 ms

common

common

30 ms

layout

layout

12 ms

graphene-global

graphene-global

15 ms

standard

standard

14 ms

gtm.js

gtm.js

209 ms

fbevents.js

fbevents.js

103 ms

exponea.min.js

exponea.min.js

637 ms

cae57a26-9def-4939-8205-8ce9bd8b4874.json

cae57a26-9def-4939-8205-8ce9bd8b4874.json

93 ms

26683.jpg

26683.jpg

296 ms

11454.jpg

11454.jpg

411 ms

26075.jpg

26075.jpg

406 ms

26688.jpg

26688.jpg

424 ms

26689.jpg

26689.jpg

425 ms

26682.jpg

26682.jpg

420 ms

26675.jpg

26675.jpg

423 ms

26674.jpg

26674.jpg

515 ms

26678.jpg

26678.jpg

521 ms

26679.jpg

26679.jpg

520 ms

26676.jpg

26676.jpg

528 ms

26681.jpg

26681.jpg

527 ms

26680.jpg

26680.jpg

527 ms

26074.jpg

26074.jpg

618 ms

26076.jpg

26076.jpg

625 ms

26706.jpg

26706.jpg

633 ms

26705.jpg

26705.jpg

633 ms

uk.svg

uk.svg

88 ms

de.svg

de.svg

85 ms

site-logo.svg

site-logo.svg

328 ms

icon-hamburger.svg

icon-hamburger.svg

86 ms

secure-shopping.svg

secure-shopping.svg

88 ms

google-pay.svg

google-pay.svg

87 ms

apple-pay.svg

apple-pay.svg

132 ms

thawte.svg

thawte.svg

131 ms

paypal.svg

paypal.svg

129 ms

visa.svg

visa.svg

132 ms

mastercard.svg

mastercard.svg

130 ms

maestro.svg

maestro.svg

174 ms

1395

1395

79 ms

d

d

49 ms

d

d

94 ms

d

d

94 ms

location

location

110 ms

otBannerSdk.js

otBannerSdk.js

27 ms

Accessibility Review

frugi.com accessibility score

84

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

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

frugi.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Page has valid source maps

SEO Factors

frugi.com SEO score

76

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Frugi.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 Frugi.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

frugi.com

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