Tools & Wizards About Us
uline.mx screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 0

    Best Practices

  • 90

    SEO

    Google-friendlier than
    68% of websites

uline.mx

Uline.mx - Cajas para Envíos, Materiales de Empaque, Materiales de Empaque, Suministros para Empaque

Page Load Speed

2 sec in total

First Response

424 ms

Resources Loaded

1.3 sec

Page Rendered

238 ms

uline.mx screenshot

About Website

Click here to check amazing Uline content for Mexico. Otherwise, check out these important facts you probably never knew about uline.mx

Uline tiene en existencia más de 41,000 cajas para envíos, materiales de empaque, productos para almacén, manejo de materiales y más. Envío el mismo día para cajas de cartón, bolsas de plástico, produ...

Visit uline.mx

Key Findings

We analyzed Uline.mx page load time and found that the first response time was 424 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

uline.mx performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value17,610 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value28.6 s

0/100

10%

Network Requests Diagram

www.uline.mx

424 ms

catalogfonts4web.css

30 ms

UlineStyles.min.css

36 ms

UlineScriptFiles.min.js

25 ms

WebResource.axd

105 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 62% of them (18 requests) were addressed to the original Uline.mx, 21% (6 requests) were made to Es.uline.mx and 7% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (424 ms) belongs to the original domain Uline.mx.

Page Optimization Overview & Recommendations

Page size can be reduced by 441.3 kB (41%)

Content Size

1.1 MB

After Optimization

643.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Uline.mx main page is 1.1 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 569.8 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 36.3 kB

  • Original 46.8 kB
  • After minification 41.5 kB
  • After compression 10.6 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 5.4 kB, which is 11% 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 36.3 kB or 77% of the original size.

Image Optimization

-11%

Potential reduce by 62.4 kB

  • Original 569.8 kB
  • After minification 507.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. Obviously, Uline needs image optimization as it can save up to 62.4 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 235.6 kB

  • Original 339.1 kB
  • After minification 332.5 kB
  • After compression 103.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 235.6 kB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 107.1 kB

  • Original 128.5 kB
  • After minification 127.7 kB
  • After compression 21.4 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. Uline.mx needs all CSS files to be minified and compressed as it can save up to 107.1 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (24%)

Requests Now

25

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.uline.mx

www.uline.mx

424 ms

catalogfonts4web.css

catalogfonts4web.css

30 ms

UlineStyles.min.css

UlineStyles.min.css

36 ms

UlineScriptFiles.min.js

UlineScriptFiles.min.js

25 ms

WebResource.axd

WebResource.axd

105 ms

mpel.js

mpel.js

129 ms

gtm.js

gtm.js

52 ms

spacer.gif

spacer.gif

20 ms

popuptopWhite.png

popuptopWhite.png

9 ms

btnclose.gif

btnclose.gif

23 ms

CloseFlyout.png

CloseFlyout.png

9 ms

feature1_MX.jpg

feature1_MX.jpg

12 ms

feature2_MX.jpg

feature2_MX.jpg

22 ms

feature3_MX.jpg

feature3_MX.jpg

20 ms

feature4_MX.jpg

feature4_MX.jpg

23 ms

43b723ac-a6f2-4d5d-9d72-c50aea85ecee.woff

43b723ac-a6f2-4d5d-9d72-c50aea85ecee.woff

52 ms

c18aee57-7585-4a8b-9a1c-69d226301d73.woff

c18aee57-7585-4a8b-9a1c-69d226301d73.woff

47 ms

HomePageSprite.png

HomePageSprite.png

28 ms

composite_MX.jpg

composite_MX.jpg

29 ms

mpel.js

mpel.js

71 ms

analytics.js

analytics.js

22 ms

collect

collect

13 ms

welcome.js

welcome.js

56 ms

collect

collect

70 ms

lightbox.css

lightbox.css

56 ms

welcome.html

welcome.html

336 ms

sprite.png

sprite.png

149 ms

el.gif

el.gif

151 ms

uline_bg_wide.png

uline_bg_wide.png

18 ms

Accessibility Review

uline.mx accessibility score

89

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

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

Some elements have a [tabindex] value greater than 0

SEO Factors

uline.mx SEO score

90

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

High

Tap targets are not sized appropriately

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 Uline.mx 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 Uline.mx 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

uline.mx

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