Tools & Wizards About Us
zarex.com.br screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 54% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

zarex.com.br

Zárex – Noivas

Page Load Speed

4.2 sec in total

First Response

340 ms

Resources Loaded

3.2 sec

Page Rendered

586 ms

zarex.com.br screenshot

About Website

Welcome to zarex.com.br homepage info - get ready to check Zarex best content right away, or after learning these important things about zarex.com.br

Visit zarex.com.br

Key Findings

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

Performance Metrics

zarex.com.br performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

39/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value9.0 s

14/100

10%

TBT (Total Blocking Time)

Value770 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

zarex.com.br

340 ms

zarex.com.br

1165 ms

styles.css

126 ms

main-style.css

250 ms

flatsome.css

502 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 78% of them (40 requests) were addressed to the original Zarex.com.br, 8% (4 requests) were made to Fonts.gstatic.com and 8% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Zarex.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 171.1 kB (15%)

Content Size

1.1 MB

After Optimization

941.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 98.2 kB

  • Original 120.8 kB
  • After minification 112.9 kB
  • After compression 22.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. 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 98.2 kB or 81% of the original size.

Image Optimization

-11%

Potential reduce by 70.9 kB

  • Original 669.1 kB
  • After minification 598.2 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. Obviously, Zarex needs image optimization as it can save up to 70.9 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 1.3 kB

  • Original 281.8 kB
  • After minification 281.8 kB
  • After compression 280.4 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

-2%

Potential reduce by 646 B

  • Original 40.4 kB
  • After minification 40.2 kB
  • After compression 39.8 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. Zarex.com.br has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 24 (55%)

Requests Now

44

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

zarex.com.br

zarex.com.br

340 ms

zarex.com.br

zarex.com.br

1165 ms

styles.css

styles.css

126 ms

main-style.css

main-style.css

250 ms

flatsome.css

flatsome.css

502 ms

flatsome-shop.css

flatsome-shop.css

375 ms

style.css

style.css

379 ms

css

css

34 ms

jquery.min.js

jquery.min.js

500 ms

jquery-migrate.min.js

jquery-migrate.min.js

383 ms

wp-polyfill.min.js

wp-polyfill.min.js

836 ms

index.js

index.js

498 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

835 ms

add-to-cart.min.js

add-to-cart.min.js

835 ms

js.cookie.min.js

js.cookie.min.js

939 ms

woocommerce.min.js

woocommerce.min.js

939 ms

cart-fragments.min.js

cart-fragments.min.js

938 ms

flatsome-live-search.js

flatsome-live-search.js

938 ms

hoverIntent.min.js

hoverIntent.min.js

938 ms

flatsome.js

flatsome.js

938 ms

flatsome-cookie-notice.js

flatsome-cookie-notice.js

1037 ms

woocommerce.js

woocommerce.js

1038 ms

elfsight-instagram-feed.js

elfsight-instagram-feed.js

1352 ms

LOGO_ZAREX-p.png

LOGO_ZAREX-p.png

1160 ms

LOGO_ZAREXb.png

LOGO_ZAREXb.png

1162 ms

scroll-arrow-e1631812021523.png

scroll-arrow-e1631812021523.png

505 ms

Florescer-Colecao-Sophia-Tolli-300x400.jpg

Florescer-Colecao-Sophia-Tolli-300x400.jpg

600 ms

Devaneio-com-Mangas-Colecao-Sophia-Tolli-300x400.jpg

Devaneio-com-Mangas-Colecao-Sophia-Tolli-300x400.jpg

721 ms

Devaneio-Colecao-Sophia-Tolli-300x400.jpg

Devaneio-Colecao-Sophia-Tolli-300x400.jpg

599 ms

star-1-300x300.png

star-1-300x300.png

721 ms

price-tag-1-300x300.png

price-tag-1-300x300.png

749 ms

LOGO_ZAREXb-1024x274.png

LOGO_ZAREXb-1024x274.png

1165 ms

LOGO_ZAREXb-1024x274.webp

LOGO_ZAREXb-1024x274.webp

1160 ms

whatsapp-2-300x300-1.webp

whatsapp-2-300x300-1.webp

1160 ms

phone-call-1-300x300.png

phone-call-1-300x300.png

1160 ms

phone-call-1-300x300-1.webp

phone-call-1-300x300-1.webp

1161 ms

email-300x300-1.webp

email-300x300-1.webp

1161 ms

place-300x300-1.webp

place-300x300-1.webp

1162 ms

artmark-ecommerce-logo-white-e1631989365551.png

artmark-ecommerce-logo-white-e1631989365551.png

1162 ms

LOGO_ZAREX-p-1-1024x274.webp

LOGO_ZAREX-p-1-1024x274.webp

1162 ms

gtm.js

gtm.js

402 ms

embed

embed

320 ms

pxiByp8kv8JHgFVrLDz8Z1xlE92JQEk.woff

pxiByp8kv8JHgFVrLDz8Z1xlE92JQEk.woff

99 ms

pxiEyp8kv8JHgFVrJJfedHFHGPc.woff

pxiEyp8kv8JHgFVrJJfedHFHGPc.woff

100 ms

pxiByp8kv8JHgFVrLGT9Z1xlE92JQEk.woff

pxiByp8kv8JHgFVrLGT9Z1xlE92JQEk.woff

128 ms

B50TF6xQr2TXJBnGOFME6u5OR83oRP5qkH7gOKoaWiA.woff

B50TF6xQr2TXJBnGOFME6u5OR83oRP5qkH7gOKoaWiA.woff

128 ms

fl-icons.ttf

fl-icons.ttf

758 ms

js

js

35 ms

search.js

search.js

5 ms

geometry.js

geometry.js

9 ms

main.js

main.js

14 ms

Accessibility Review

zarex.com.br accessibility score

83

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

<frame> or <iframe> elements do not have a title

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

zarex.com.br 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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

zarex.com.br SEO score

92

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

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zarex.com.br can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Zarex.com.br 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

zarex.com.br

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