Tools & Wizards About Us
patioparfum.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

patioparfum.com

PATIO: Online store of perfumes and natural cosmetics

Page Load Speed

2.6 sec in total

First Response

200 ms

Resources Loaded

2.1 sec

Page Rendered

305 ms

patioparfum.com screenshot

About Website

Welcome to patioparfum.com homepage info - get ready to check PATIO Parfum best content right away, or after learning these important things about patioparfum.com

Online store where you can buy perfumes and natural cosmetics at competitive prices.

Visit patioparfum.com

Key Findings

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

Performance Metrics

patioparfum.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

6/100

10%

LCP (Largest Contentful Paint)

Value8.5 s

1/100

25%

SI (Speed Index)

Value6.5 s

39/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.829

4/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

patioparfum.com

200 ms

en.patioparfum.com

516 ms

js

80 ms

css

52 ms

bootstrap.min.css

164 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Patioparfum.com, 84% (41 requests) were made to En.patioparfum.com and 4% (2 requests) were made to Maxcdn.bootstrapcdn.com. The less responsive or slowest element that took the longest time to load (530 ms) relates to the external source En.patioparfum.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 102.5 kB (8%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 75.5 kB

  • Original 89.8 kB
  • After minification 87.3 kB
  • After compression 14.3 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 75.5 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 19.0 kB

  • Original 1.1 MB
  • After minification 1.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. PATIO Parfum images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 2.6 kB

  • Original 161.2 kB
  • After minification 161.2 kB
  • After compression 158.6 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

-14%

Potential reduce by 5.4 kB

  • Original 38.8 kB
  • After minification 38.8 kB
  • After compression 33.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. Patioparfum.com needs all CSS files to be minified and compressed as it can save up to 5.4 kB or 14% of the original size.

Requests Breakdown

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

Requests Now

43

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

patioparfum.com

patioparfum.com

200 ms

en.patioparfum.com

en.patioparfum.com

516 ms

js

js

80 ms

css

css

52 ms

bootstrap.min.css

bootstrap.min.css

164 ms

font-awesome.min.css

font-awesome.min.css

61 ms

stylesv4.css

stylesv4.css

248 ms

suggester.css

suggester.css

255 ms

sexyalertbox.css

sexyalertbox.css

252 ms

utils.js

utils.js

259 ms

jquery-1.12.3.min.js

jquery-1.12.3.min.js

365 ms

jquery-ui-1.11.4.min.js

jquery-ui-1.11.4.min.js

481 ms

jquery-ui.css

jquery-ui.css

35 ms

index-slider.js

index-slider.js

328 ms

mootools-1.2.5-core.js

mootools-1.2.5-core.js

415 ms

mootools-1.2.5.1-more.js

mootools-1.2.5.1-more.js

415 ms

mootools-1.2.4_extends.js

mootools-1.2.4_extends.js

341 ms

bootstrap.min.js

bootstrap.min.js

410 ms

formCheckMsg.js

formCheckMsg.js

425 ms

adminAccount.js

adminAccount.js

452 ms

dataCheck.js

dataCheck.js

528 ms

jssor.slider.mini.js

jssor.slider.mini.js

530 ms

sexyalertbox.v1.2.moo.mini.js

sexyalertbox.v1.2.moo.mini.js

529 ms

logo-patio2.png

logo-patio2.png

96 ms

index_phone_spacer.png

index_phone_spacer.png

94 ms

index_pc_spacer.png

index_pc_spacer.png

97 ms

01308.jpg

01308.jpg

99 ms

01328.jpg

01328.jpg

96 ms

01310.jpg

01310.jpg

97 ms

00969.jpg

00969.jpg

238 ms

01148.jpg

01148.jpg

239 ms

01272.jpg

01272.jpg

161 ms

01220.jpg

01220.jpg

250 ms

01041.jpg

01041.jpg

175 ms

00967.jpg

00967.jpg

183 ms

90001_taller_iniciacion.jpg

90001_taller_iniciacion.jpg

320 ms

90002_taller_creacion.jpg

90002_taller_creacion.jpg

351 ms

visitarPatio.jpg

visitarPatio.jpg

366 ms

visitarPatio-xs.jpg

visitarPatio-xs.jpg

395 ms

x_close_white.png

x_close_white.png

317 ms

en-encense-phone.jpg

en-encense-phone.jpg

412 ms

en-encense-pc.jpg

en-encense-pc.jpg

388 ms

bg-box-bottom.png

bg-box-bottom.png

307 ms

bg-box-top.png

bg-box-top.png

345 ms

bg-box-body.png

bg-box-body.png

366 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

21 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

25 ms

patioIcons.ttf

patioIcons.ttf

374 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

25 ms

Accessibility Review

patioparfum.com accessibility score

93

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

Links do not have a discernible name

Best Practices

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

patioparfum.com SEO score

90

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

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

patioparfum.com

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