Tools & Wizards About Us

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 81

    SEO

    Google-friendlier than
    42% of websites

websimples.info

Criação de sites em Belém | WSB - Web Simples Brasil | Produtora de Sites | Desenvolvimento de Sites em Belém

Page Load Speed

4.3 sec in total

First Response

621 ms

Resources Loaded

3.3 sec

Page Rendered

362 ms

About Website

Click here to check amazing Web Simples content for Brazil. Otherwise, check out these important facts you probably never knew about websimples.info

Criação de Sites em Belém, Desenvolvimento de Sites, Homepages, Blogs, Hotsites e Portais. Envio de e-mail marketing em Belém e SMS corporativo

Visit websimples.info

Key Findings

We analyzed Websimples.info page load time and found that the first response time was 621 ms and then it took 3.7 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

websimples.info performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value7.0 s

6/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.038

100/100

15%

TTI (Time to Interactive)

Value7.3 s

49/100

10%

Network Requests Diagram

websimples.info

621 ms

websimples.info

588 ms

estilos.css

265 ms

css_menu.css

398 ms

modal_video.css

400 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 82% of them (37 requests) were addressed to the original Websimples.info, 9% (4 requests) were made to Use.fontawesome.com and 7% (3 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Websimples.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 354.4 kB (28%)

Content Size

1.3 MB

After Optimization

923.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Websimples.info main page is 1.3 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. 40% of websites need less resources to load. Images take 905.4 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 29.8 kB

  • Original 34.8 kB
  • After minification 20.6 kB
  • After compression 5.0 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 14.2 kB, which is 41% 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 29.8 kB or 86% of the original size.

Image Optimization

-10%

Potential reduce by 88.0 kB

  • Original 905.4 kB
  • After minification 817.4 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. Web Simples images are well optimized though.

JavaScript Optimization

-71%

Potential reduce by 200.3 kB

  • Original 281.8 kB
  • After minification 249.6 kB
  • After compression 81.5 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 200.3 kB or 71% of the original size.

CSS Optimization

-66%

Potential reduce by 36.3 kB

  • Original 55.4 kB
  • After minification 45.7 kB
  • After compression 19.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. Websimples.info needs all CSS files to be minified and compressed as it can save up to 36.3 kB or 66% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (27%)

Requests Now

37

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

websimples.info accessibility score

59

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

Image elements do not have [alt] attributes

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

websimples.info best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

websimples.info SEO score

81

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Websimples.info 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 Websimples.info main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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