Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 66

    SEO

    Google-friendlier than
    25% of websites

censtry.pt

Componentes eletrônicos de balcão único, chips IC de circuito integrado, site de serviço de suporte técnico | Censtry.pt

Page Load Speed

32.9 sec in total

First Response

421 ms

Resources Loaded

30.6 sec

Page Rendered

1.8 sec

censtry.pt screenshot

About Website

Welcome to censtry.pt homepage info - get ready to check Censtry best content right away, or after learning these important things about censtry.pt

Censtry Electronics é um distribuidor global de componentes eletrônicos, nosso site é uma plataforma de fornecimento on-line completa. Fornecemos componentes eletrônicos com o melhor preço, novo origi...

Visit censtry.pt

Key Findings

We analyzed Censtry.pt page load time and found that the first response time was 421 ms and then it took 32.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

censtry.pt performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value22.9 s

0/100

10%

TBT (Total Blocking Time)

Value380 ms

69/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value11.4 s

19/100

10%

Network Requests Diagram

censtry.pt

421 ms

www.censtry.pt

1241 ms

js

53 ms

all.min.css

862 ms

bootstrap.min.css

2589 ms

Our browser made a total of 145 requests to load all elements on the main page. We found that 87% of them (126 requests) were addressed to the original Censtry.pt, 9% (13 requests) were made to Embed.tawk.to and 1% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Censtry.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 344.9 kB (19%)

Content Size

1.8 MB

After Optimization

1.4 MB

In fact, the total size of Censtry.pt main page is 1.8 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. 60% of websites need less resources to load. Images take 997.2 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 252.0 kB

  • Original 314.5 kB
  • After minification 219.9 kB
  • After compression 62.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. This page needs HTML code to be minified as it can gain 94.5 kB, which is 30% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 252.0 kB or 80% of the original size.

Image Optimization

-7%

Potential reduce by 64.9 kB

  • Original 997.2 kB
  • After minification 932.3 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. Censtry images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 27.7 kB

  • Original 370.8 kB
  • After minification 370.8 kB
  • After compression 343.1 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 275 B

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

Requests Breakdown

Number of requests can be reduced by 31 (22%)

Requests Now

139

After Optimization

108

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

Accessibility Review

censtry.pt accessibility score

85

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

Image elements do not have [alt] attributes

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

censtry.pt best practices score

67

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

censtry.pt SEO score

66

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

    EN

  • Language Claimed

    PT

  • Encoding

    UTF-8

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

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