Tools & Wizards About Us
ottawa.com.br screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

ottawa.com.br

Plataforma Ecommerce e Loja Virtual Online - Dooca Commerce

Page Load Speed

2.9 sec in total

First Response

547 ms

Resources Loaded

2.3 sec

Page Rendered

70 ms

ottawa.com.br screenshot

About Website

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

Plataforma Ecommerce perfeita para sua loja virtual. Veja como criar uma loja virtual na Dooca Commerce é simples e rápido.

Visit ottawa.com.br

Key Findings

We analyzed Ottawa.com.br page load time and found that the first response time was 547 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

ottawa.com.br performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value6.1 s

44/100

10%

TBT (Total Blocking Time)

Value860 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.089

92/100

15%

TTI (Time to Interactive)

Value9.0 s

34/100

10%

Network Requests Diagram

ottawa.com.br

547 ms

www.dooca.com.br

227 ms

js

147 ms

index.6572e03a.css

55 ms

embed.php

252 ms

Our browser made a total of 21 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Ottawa.com.br, 24% (5 requests) were made to Fonts.gstatic.com and 14% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (895 ms) relates to the external source Connect.facebook.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 14.1 kB (16%)

Content Size

89.2 kB

After Optimization

75.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-77%

Potential reduce by 14.0 kB

  • Original 18.1 kB
  • After minification 17.7 kB
  • After compression 4.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 14.0 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 39.9 kB
  • After minification 39.9 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. Ottawa images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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 37 B

  • Original 10.1 kB
  • After minification 10.1 kB
  • After compression 10.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. Ottawa.com.br has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 7 (50%)

Requests Now

14

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ottawa.com.br

ottawa.com.br

547 ms

www.dooca.com.br

www.dooca.com.br

227 ms

js

js

147 ms

index.6572e03a.css

index.6572e03a.css

55 ms

embed.php

embed.php

252 ms

css2

css2

174 ms

css

css

185 ms

analytics.js

analytics.js

165 ms

fbevents.js

fbevents.js

152 ms

0205fa65-2455-4ccd-9005-b91c064fa381.jpeg

0205fa65-2455-4ccd-9005-b91c064fa381.jpeg

367 ms

esfkyjh1u_forms-close-dark.png

esfkyjh1u_forms-close-dark.png

364 ms

css2

css2

60 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

313 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

321 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

320 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff

320 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff

318 ms

134909303735004

134909303735004

895 ms

collect

collect

22 ms

collect

collect

31 ms

ga-audiences

ga-audiences

74 ms

Accessibility Review

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

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

ottawa.com.br SEO score

87

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

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

    EN

  • Encoding

    UTF-8

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

ottawa.com.br

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