Tools & Wizards About Us
pulltex.com screenshot

Report Summary

  • 2

    Performance

    Renders faster than
    20% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

pulltex.com

SACACORCHOS Y ACCESORIOS DE VINO | PULLTEX

Page Load Speed

3.3 sec in total

First Response

537 ms

Resources Loaded

2.6 sec

Page Rendered

189 ms

pulltex.com screenshot

About Website

Click here to check amazing PULLTEX content for Russia. Otherwise, check out these important facts you probably never knew about pulltex.com

Pulltex es la marca de sacacorchos y accesorios de vino más importante del mercado. Los sacacorchos profesionales Pulltex están avalados por más de 20 patentes internacionales. Pulltex es se caract...

Visit pulltex.com

Key Findings

We analyzed Pulltex.com page load time and found that the first response time was 537 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

pulltex.com performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value11.9 s

0/100

25%

SI (Speed Index)

Value26.9 s

0/100

10%

TBT (Total Blocking Time)

Value3,010 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.883

3/100

15%

TTI (Time to Interactive)

Value24.7 s

0/100

10%

Network Requests Diagram

537 ms

styles.css

217 ms

youtube.css

199 ms

widgets.css

203 ms

prototype.js

437 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 93% of them (52 requests) were addressed to the original Pulltex.com, 4% (2 requests) were made to Beetailer.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (890 ms) belongs to the original domain Pulltex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 535.6 kB (29%)

Content Size

1.8 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pulltex.com 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. 45% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 16.5 kB

  • Original 21.8 kB
  • After minification 19.5 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 16.5 kB or 76% of the original size.

Image Optimization

-2%

Potential reduce by 22.4 kB

  • Original 1.2 MB
  • After minification 1.2 MB

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. PULLTEX images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 406.6 kB

  • Original 535.3 kB
  • After minification 414.8 kB
  • After compression 128.8 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 406.6 kB or 76% of the original size.

CSS Optimization

-87%

Potential reduce by 90.2 kB

  • Original 103.7 kB
  • After minification 76.0 kB
  • After compression 13.5 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. Pulltex.com needs all CSS files to be minified and compressed as it can save up to 90.2 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (45%)

Requests Now

55

After Optimization

30

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

537 ms

styles.css

styles.css

217 ms

youtube.css

youtube.css

199 ms

widgets.css

widgets.css

203 ms

prototype.js

prototype.js

437 ms

ccard.js

ccard.js

216 ms

validation.js

validation.js

220 ms

builder.js

builder.js

297 ms

effects-1.9.js

effects-1.9.js

304 ms

dragdrop.js

dragdrop.js

322 ms

controls.js

controls.js

323 ms

slider.js

slider.js

324 ms

js.js

js.js

395 ms

form.js

form.js

403 ms

menu.js

menu.js

429 ms

translate.js

translate.js

430 ms

cookies.js

cookies.js

430 ms

jquery.js

jquery.js

592 ms

fondo.js

fondo.js

502 ms

youtube.js

youtube.js

536 ms

slideshow.js

slideshow.js

537 ms

lightbox.js

lightbox.js

537 ms

funciones_jquery.js

funciones_jquery.js

536 ms

interaktingslider.js

interaktingslider.js

623 ms

beetailer.js

beetailer.js

44 ms

ga.js

ga.js

24 ms

header.png

header.png

112 ms

logo.png

logo.png

111 ms

search.png

search.png

104 ms

search_submit.png

search_submit.png

111 ms

tit_empresa_en.jpg

tit_empresa_en.jpg

99 ms

pulltex_empresa_img.jpg

pulltex_empresa_img.jpg

201 ms

Untitled-7.jpg

Untitled-7.jpg

294 ms

area_en.png

area_en.png

308 ms

bg_container_nav.png

bg_container_nav.png

413 ms

__utm.gif

__utm.gif

31 ms

monzaB2017.jpg

monzaB2017.jpg

275 ms

pulltex_slideCork.png

pulltex_slideCork.png

526 ms

std2017.png

std2017.png

554 ms

freeAppbanner.png

freeAppbanner.png

445 ms

monza2017.jpg

monza2017.jpg

367 ms

bullet.png

bullet.png

382 ms

share_wine_en.png

share_wine_en.png

469 ms

share_email.png

share_email.png

488 ms

share_facebook.png

share_facebook.png

489 ms

share_twitter.png

share_twitter.png

542 ms

share_youtube.png

share_youtube.png

571 ms

share_flickr.png

share_flickr.png

594 ms

share_cart.png

share_cart.png

596 ms

bg_container.png

bg_container.png

631 ms

bg_container.jpg

bg_container.jpg

639 ms

footer.png

footer.png

652 ms

bullet_active.png

bullet_active.png

650 ms

bg2.jpg

bg2.jpg

890 ms

print.css

print.css

108 ms

promotions.js

promotions.js

1 ms

Accessibility Review

pulltex.com accessibility score

74

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

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

pulltex.com best practices score

58

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

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

pulltex.com SEO score

75

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

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

High

Tap targets are not sized appropriately

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

pulltex.com

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