Report Summary

  • 23

    Performance

    Renders faster than
    42% of other websites

  • 58

    Accessibility

    Visual factors better than
    that of 25% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

jbnet.pt

O seu fornecedor em Papelaria, Economato, Brinquedos | JBnet.pt

Page Load Speed

5.4 sec in total

First Response

306 ms

Resources Loaded

4.8 sec

Page Rendered

262 ms

jbnet.pt screenshot

About Website

Welcome to jbnet.pt homepage info - get ready to check JBnet best content for Portugal right away, or after learning these important things about jbnet.pt

Compre online aos melhores preços de revenda de papelaria, economato, brinquedos e muito mais. Portes gratis e receba premios do clube VIP.

Visit jbnet.pt

Key Findings

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

Performance Metrics

jbnet.pt performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value13.5 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value700 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.267

46/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

jbnet.pt

306 ms

www.jbnet.pt

1776 ms

bootstrap.min.css

138 ms

bootstrap-theme.min.css

85 ms

font-awesome.min.css

88 ms

Our browser made a total of 16 requests to load all elements on the main page. We found that 25% of them (4 requests) were addressed to the original Jbnet.pt, 38% (6 requests) were made to Cdn.jsdelivr.net and 25% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Jbnet.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 233.4 kB (82%)

Content Size

284.6 kB

After Optimization

51.2 kB

In fact, the total size of Jbnet.pt main page is 284.6 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. 25% of websites need less resources to load. CSS take 173.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 88.9 kB

  • Original 111.1 kB
  • After minification 105.8 kB
  • After compression 22.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 88.9 kB or 80% of the original size.

CSS Optimization

-83%

Potential reduce by 144.5 kB

  • Original 173.5 kB
  • After minification 173.2 kB
  • After compression 28.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. Jbnet.pt needs all CSS files to be minified and compressed as it can save up to 144.5 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

9

After Optimization

2

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

Accessibility Review

jbnet.pt accessibility score

58

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

jbnet.pt SEO score

92

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

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Jbnet.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Jbnet.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 JBnet. 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: