Report Summary

  • 85

    Performance

    Renders faster than
    89% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

postubo.com

PosTubo - Conocimiento colectivo

Page Load Speed

482 ms in total

First Response

52 ms

Resources Loaded

221 ms

Page Rendered

209 ms

postubo.com screenshot

About Website

Visit postubo.com now to see the best up-to-date Pos Tubo content for Spain and also check out these interesting facts you probably never knew about postubo.com

PosTubo es una comunidad de usuari@s interesad@s en conversar, debatir y compartir información.

Visit postubo.com

Key Findings

We analyzed Postubo.com page load time and found that the first response time was 52 ms and then it took 430 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

postubo.com performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value2.6 s

97/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.0 s

64/100

10%

Network Requests Diagram

postubo.com

52 ms

cloudflare.min.js

9 ms

4ca970f7f141.css

28 ms

3b6e343ba217.css

67 ms

style.css

26 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 67% of them (6 requests) were addressed to the original Postubo.com, 11% (1 request) were made to Ajax.cloudflare.com and 11% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (67 ms) belongs to the original domain Postubo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 198.3 kB (78%)

Content Size

253.4 kB

After Optimization

55.1 kB

In fact, the total size of Postubo.com main page is 253.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. 20% of websites need less resources to load. CSS take 137.7 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 23.9 kB

  • Original 29.2 kB
  • After minification 29.2 kB
  • After compression 5.3 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 23.9 kB or 82% of the original size.

JavaScript Optimization

-69%

Potential reduce by 59.9 kB

  • Original 86.5 kB
  • After minification 86.5 kB
  • After compression 26.6 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 59.9 kB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 114.5 kB

  • Original 137.7 kB
  • After minification 132.8 kB
  • After compression 23.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. Postubo.com needs all CSS files to be minified and compressed as it can save up to 114.5 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

6

After Optimization

3

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pos Tubo. 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 CSS and as a result speed up the page load time.

Accessibility Review

postubo.com accessibility score

72

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

postubo.com 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

postubo.com SEO score

83

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

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Postubo.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Postubo.com 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 data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: