Tools & Wizards About Us
unefleur.com.br screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

unefleur.com.br

Floricultura em São Paulo - Flores, arranjos, bouquets - Une Fleur

Page Load Speed

5.3 sec in total

First Response

368 ms

Resources Loaded

3.9 sec

Page Rendered

1.1 sec

unefleur.com.br screenshot

About Website

Visit unefleur.com.br now to see the best up-to-date Une Fleur content and also check out these interesting facts you probably never knew about unefleur.com.br

Entrega de Flores em São Paulo. Arranjos de flores, bouquets, rosas. Requinte em personalização de arranjos. Decoração p/ empresas e eventos.

Visit unefleur.com.br

Key Findings

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

Performance Metrics

unefleur.com.br performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value7.8 s

23/100

10%

TBT (Total Blocking Time)

Value260 ms

83/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value8.2 s

40/100

10%

Network Requests Diagram

unefleur.com.br

368 ms

floresemsp.com.br

752 ms

f27cdde0825c5cde7260baf350fc6abd.css

265 ms

js

63 ms

float.js

513 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Unefleur.com.br, 93% (27 requests) were made to Floresemsp.com.br and 3% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (754 ms) relates to the external source Floresemsp.com.br.

Page Optimization Overview & Recommendations

Page size can be reduced by 184.5 kB (45%)

Content Size

410.4 kB

After Optimization

225.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Unefleur.com.br main page is 410.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. HTML takes 220.2 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 183.8 kB

  • Original 220.2 kB
  • After minification 219.8 kB
  • After compression 36.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 183.8 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 71 B

  • Original 84.2 kB
  • After minification 84.1 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. Une Fleur images are well optimized though.

JavaScript Optimization

-5%

Potential reduce by 346 B

  • Original 6.7 kB
  • After minification 6.7 kB
  • After compression 6.3 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 233 B

  • Original 99.3 kB
  • After minification 99.3 kB
  • After compression 99.1 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. Unefleur.com.br has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

22

After Optimization

22

  • Images
  • JavaScript
  • CSS

The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Une Fleur. According to our analytics all requests are already optimized.

Network Requests Diagram

unefleur.com.br

unefleur.com.br

368 ms

floresemsp.com.br

floresemsp.com.br

752 ms

f27cdde0825c5cde7260baf350fc6abd.css

f27cdde0825c5cde7260baf350fc6abd.css

265 ms

js

js

63 ms

float.js

float.js

513 ms

Banner-desktop.webp

Banner-desktop.webp

250 ms

bouquets-desktop-copiar.webp

bouquets-desktop-copiar.webp

254 ms

Banner-mobile.webp

Banner-mobile.webp

375 ms

bouquets-mobile-copiar.webp

bouquets-mobile-copiar.webp

501 ms

lazy.png

lazy.png

378 ms

Realife-Moment-Italic-1.woff

Realife-Moment-Italic-1.woff

378 ms

fa-solid-900.woff

fa-solid-900.woff

407 ms

ionicons.woff

ionicons.woff

498 ms

eicons.woff

eicons.woff

754 ms

fa-brands-400.woff

fa-brands-400.woff

633 ms

Marca-Grafica_Completo_Preto_Com-tagline-scaled.webp

Marca-Grafica_Completo_Preto_Com-tagline-scaled.webp

128 ms

Marca-Grafica_Reduzido_Preto_Sem-tagline.webp

Marca-Grafica_Reduzido_Preto_Sem-tagline.webp

130 ms

unnamed-2.png

unnamed-2.png

129 ms

unnamed-3.png

unnamed-3.png

130 ms

unnamed.png

unnamed.png

132 ms

unnamed-4.png

unnamed-4.png

132 ms

Eduardo-Costa.png

Eduardo-Costa.png

252 ms

unnamed-5.png

unnamed-5.png

254 ms

unnamed.png

unnamed.png

255 ms

unnamed-5-1.png

unnamed-5-1.png

254 ms

unnamed-3.png

unnamed-3.png

256 ms

unnamed-1.png

unnamed-1.png

256 ms

unnamed-2.png

unnamed-2.png

376 ms

unnamed-4.png

unnamed-4.png

381 ms

Accessibility Review

unefleur.com.br accessibility score

88

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

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

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

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

unefleur.com.br SEO score

91

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

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

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

unefleur.com.br

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