Tools & Wizards About Us
crane.mx screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

crane.mx

crane.mx

Page Load Speed

1.9 sec in total

First Response

93 ms

Resources Loaded

1.3 sec

Page Rendered

556 ms

crane.mx screenshot

About Website

Visit crane.mx now to see the best up-to-date Crane content and also check out these interesting facts you probably never knew about crane.mx

Visit crane.mx

Key Findings

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

Performance Metrics

crane.mx performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

91/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value3.7 s

85/100

10%

TBT (Total Blocking Time)

Value70 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.548

13/100

15%

TTI (Time to Interactive)

Value7.5 s

47/100

10%

Network Requests Diagram

crane.mx

93 ms

stylesheet.css

45 ms

preloads.js

171 ms

load_feature-87876fa245af19cbd14aa886ed59c6aa8a27c45d24dcd7a81cf2d2323506233e.js

39 ms

features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js

43 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 81% of them (22 requests) were addressed to the original Crane.mx, 7% (2 requests) were made to Instagrid.instasell.co.in and 7% (2 requests) were made to Cdn.shopify.com. The less responsive or slowest element that took the longest time to load (931 ms) belongs to the original domain Crane.mx.

Page Optimization Overview & Recommendations

Page size can be reduced by 174.5 kB (4%)

Content Size

4.0 MB

After Optimization

3.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Crane.mx main page is 4.0 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 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 119.3 kB

  • Original 145.1 kB
  • After minification 126.2 kB
  • After compression 25.8 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 18.9 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 119.3 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 3.6 MB
  • After minification 3.6 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. Crane images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 32.3 kB

  • Original 203.0 kB
  • After minification 203.0 kB
  • After compression 170.7 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 32.3 kB or 16% of the original size.

CSS Optimization

-33%

Potential reduce by 22.9 kB

  • Original 68.4 kB
  • After minification 68.4 kB
  • After compression 45.6 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. Crane.mx needs all CSS files to be minified and compressed as it can save up to 22.9 kB or 33% of the original size.

Requests Breakdown

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

Requests Now

26

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

crane.mx

crane.mx

93 ms

stylesheet.css

stylesheet.css

45 ms

preloads.js

preloads.js

171 ms

load_feature-87876fa245af19cbd14aa886ed59c6aa8a27c45d24dcd7a81cf2d2323506233e.js

load_feature-87876fa245af19cbd14aa886ed59c6aa8a27c45d24dcd7a81cf2d2323506233e.js

39 ms

features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js

features-1c0b396bd4d054b94abae1eb6a1bd6ba47beb35525c57a217c77a862ff06d83f.js

43 ms

index.js

index.js

175 ms

index.css

index.css

192 ms

eventemitter3.min.js

eventemitter3.min.js

158 ms

vendor-video.js

vendor-video.js

157 ms

theme.js

theme.js

159 ms

css

css

167 ms

whatsapp-sharing.css

whatsapp-sharing.css

171 ms

whatsapp-sharing.js

whatsapp-sharing.js

180 ms

trekkie.storefront.64022fdadec5c8ec4be5f67dbeb0521916405ce3.min.js

trekkie.storefront.64022fdadec5c8ec4be5f67dbeb0521916405ce3.min.js

113 ms

shop_events_listener-a7c63dba65ccddc484f77541dc8ca437e60e1e9e297fe1c3faebf6523a0ede9b.js

shop_events_listener-a7c63dba65ccddc484f77541dc8ca437e60e1e9e297fe1c3faebf6523a0ede9b.js

119 ms

shopify-boomerang-1.0.0.min.js

shopify-boomerang-1.0.0.min.js

115 ms

logo.jpg

logo.jpg

153 ms

Slider_Full_-_Moto.jpg

Slider_Full_-_Moto.jpg

508 ms

banner_255781d6-dac4-40bd-bbea-48612cd70505.png

banner_255781d6-dac4-40bd-bbea-48612cd70505.png

931 ms

img_playera_1.jpg

img_playera_1.jpg

153 ms

img_camisa3.jpg

img_camisa3.jpg

156 ms

img_polo1.jpg

img_polo1.jpg

151 ms

img_ninos.jpg

img_ninos.jpg

152 ms

img_dama2.jpg

img_dama2.jpg

153 ms

img_bebes.jpg

img_bebes.jpg

156 ms

img_sueter3.jpg

img_sueter3.jpg

154 ms

WhatsApp_Image_2023-06-12_at_12.49.08_PM.jpg

WhatsApp_Image_2023-06-12_at_12.49.08_PM.jpg

156 ms

Accessibility Review

crane.mx accessibility score

96

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

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

Links do not have a discernible name

Best Practices

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

SEO Factors

crane.mx SEO score

84

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

    EN

  • Language Claimed

    ES

  • Encoding

    UTF-8

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

crane.mx

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