Tools & Wizards About Us
bto.pt screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    47% of other websites

  • 87

    Accessibility

    Visual factors better than
    that of 66% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

bto.pt

Besides the Obvious | Agência de Marketing e Comunicação

Page Load Speed

17.1 sec in total

First Response

370 ms

Resources Loaded

16.5 sec

Page Rendered

253 ms

bto.pt screenshot

About Website

Visit bto.pt now to see the best up-to-date Bto content and also check out these interesting facts you probably never knew about bto.pt

Especialistas em soluções integradas de marketing e comunicação. Consultoria, gestão e desenvolvimento de marcas, planeamento de marketing.

Visit bto.pt

Key Findings

We analyzed Bto.pt page load time and found that the first response time was 370 ms and then it took 16.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster.

Performance Metrics

bto.pt performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

45/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value7.7 s

25/100

10%

TBT (Total Blocking Time)

Value860 ms

33/100

30%

CLS (Cumulative Layout Shift)

Value0.194

63/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

bto.pt

370 ms

bto.pt

11546 ms

a5ff7.css

2641 ms

8c1b4.css

510 ms

css

1315 ms

Our browser made a total of 39 requests to load all elements on the main page. We found that 69% of them (27 requests) were addressed to the original Bto.pt, 21% (8 requests) were made to Fonts.gstatic.com and 8% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (11.5 sec) belongs to the original domain Bto.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 122.6 kB (55%)

Content Size

224.2 kB

After Optimization

101.7 kB

  • HTML
  • CSS

In fact, the total size of Bto.pt main page is 224.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. 40% of websites need less resources to load. HTML takes 147.0 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 122.6 kB

  • Original 147.0 kB
  • After minification 147.0 kB
  • After compression 24.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 122.6 kB or 83% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 77.2 kB
  • After minification 77.2 kB
  • After compression 77.2 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. Bto.pt has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 11 (42%)

Requests Now

26

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

bto.pt

bto.pt

370 ms

bto.pt

bto.pt

11546 ms

a5ff7.css

a5ff7.css

2641 ms

8c1b4.css

8c1b4.css

510 ms

css

css

1315 ms

7cfc5.css

7cfc5.css

318 ms

css

css

1333 ms

d52ed.js

d52ed.js

3029 ms

ee2cb.js

ee2cb.js

3220 ms

css

css

1337 ms

f8b57.js

f8b57.js

3934 ms

525ef.js

525ef.js

4325 ms

2a86d.js

2a86d.js

3840 ms

1615d.js

1615d.js

4294 ms

gtm.js

gtm.js

243 ms

setion-red-bg.webp

setion-red-bg.webp

271 ms

slider-strawberry.webp

slider-strawberry.webp

344 ms

aeg-logo.webp

aeg-logo.webp

367 ms

berner-logo.webp

berner-logo.webp

459 ms

eletrolux-logo.webp

eletrolux-logo.webp

490 ms

fox-media-logo.webp

fox-media-logo.webp

585 ms

lexmark-logo.webp

lexmark-logo.webp

611 ms

renault-logo.webp

renault-logo.webp

702 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUhiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUhiYA.ttf

22 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs169vsUZiYA.ttf

40 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUhiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs13FvsUhiYA.ttf

87 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUhiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUhiYA.ttf

99 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvsUZiYA.ttf

99 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUhiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs18NvsUhiYA.ttf

100 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUhiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1y9osUhiYA.ttf

101 ms

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUhiYA.ttf

TK3_WkUHHAIjg75cFRf3bXL8LICs1xZosUhiYA.ttf

100 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

698 ms

fa-solid-900.woff

fa-solid-900.woff

921 ms

fa-brands-400.woff

fa-brands-400.woff

811 ms

logo-300x300.webp

logo-300x300.webp

121 ms

smush-lazyloader-1.gif

smush-lazyloader-1.gif

145 ms

setion-services-bg-2.webp

setion-services-bg-2.webp

216 ms

setion-red-bg.webp

setion-red-bg.webp

137 ms

setion-office-bg.webp

setion-office-bg.webp

229 ms

Accessibility Review

bto.pt accessibility score

87

Accessibility Issues

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

Image elements do not have [alt] attributes

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

bto.pt best practices score

92

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

Page has valid source maps

SEO Factors

bto.pt SEO score

84

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Bto.pt 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 Bto.pt 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

bto.pt

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