Access bigbuy.es. Mayorista dropshipping líder en Europa | BigBuy venta al por mayor

bigbuy.es screenshot

7

Performance

Renders faster than
22% of other websites
61

Accessibility

Visual factors better than
that of 27% of websites
75

Best Practices

More advanced features
available than in
35% of websites
79

SEO

Google-friendlier than
40% of websites

First Response

2.7 sec

Resources Loaded

73.2 sec

Page Rendered

1 sec

bigbuy.es screenshot

About Website

Click here to check amazing Big Buy content. Otherwise, check out these important facts you probably never knew about bigbuy.es

Somos el mayorista dropshipping que necesita. Miles de productos al mejor precio en nuestro tienda online B2B. Empiece a vender hoy mismo con BigBuy.

Visit bigbuy.es

Key Findings

We analyzed Bigbuy.es page load time and found that the first response time was 2.7 sec and then it took 74.2 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 90 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

name

value

score

weighting

FCP (First Contentful Paint)

Value7.5 s

1/100

10%

LCP (Largest Contentful Paint)

Value25.1 s

0/100

25%

SI (Speed Index)

Value25.7 s

0/100

10%

TBT (Total Blocking Time)

Value10,150 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.256

48/100

15%

TTI (Time to Interactive)

Value30.7 s

0/100

10%

www.bigbuy.eu

2685 ms

aos.js

47 ms

jquery-1.9.1.min.js

1774 ms

jquery.lazyload.min.js

1662 ms

aslider.js

1658 ms

Our browser made a total of 152 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Bigbuy.es, 1% (2 requests) were made to Unpkg.com and 1% (2 requests) were made to Dev.visualwebsiteoptimizer.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source Bigbuy.eu.

Content Size

307.9 kB

After Optimization

139.8 kB

In fact, the total size of Bigbuy.es main page is 307.9 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. 30% of websites need less resources to load. HTML takes 180.0 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 154.0 kB

Original 180.0 kB
After minification 155.8 kB
After compression 26.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 24.2 kB, which is 13% 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 154.0 kB or 86% of the original size.

Image Optimization

-27%

Potential reduce by 4.7 kB

Original 17.2 kB
After minification 12.5 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. Obviously, Big Buy needs image optimization as it can save up to 4.7 kB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-8%

Potential reduce by 9.4 kB

Original 110.7 kB
After minification 110.7 kB
After compression 101.3 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.

Requests Now

60

After Optimization

22

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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.

High

ARIA IDs are not unique

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

Language and Encoding

Language Detected

ES
Language Claimed

EN
Encoding

UTF-8

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

bigbuy.es

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