Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

lugex.com

Luggage Forward® - Shipping & Luggage Delivery Worldwide Since 2005

Page Load Speed

2.4 sec in total

First Response

77 ms

Resources Loaded

1.2 sec

Page Rendered

1.1 sec

lugex.com screenshot

About Website

Visit lugex.com now to see the best up-to-date Lugex content and also check out these interesting facts you probably never knew about lugex.com

Luggage Forward - the world's most trusted luggage shipping service since 2005. Every bag guaranteed on time. Worldwide service. Call 24/7 or book online.

Visit lugex.com

Key Findings

We analyzed Lugex.com page load time and found that the first response time was 77 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

lugex.com performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

77/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value3.9 s

83/100

10%

TBT (Total Blocking Time)

Value220 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.08

94/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

lugex.com

77 ms

www.luggageforward.com

478 ms

style.css

18 ms

style.css

33 ms

style.min.css

23 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lugex.com, 95% (80 requests) were made to Luggageforward.com and 1% (1 request) were made to Widget.trustpilot.com. The less responsive or slowest element that took the longest time to load (486 ms) relates to the external source Luggageforward.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 142.4 kB (13%)

Content Size

1.1 MB

After Optimization

959.8 kB

In fact, the total size of Lugex.com 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 596.1 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 135.3 kB

  • Original 161.4 kB
  • After minification 154.4 kB
  • After compression 26.1 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 135.3 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 63 B

  • Original 596.1 kB
  • After minification 596.1 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. Lugex images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.7 kB

  • Original 272.7 kB
  • After minification 272.7 kB
  • After compression 271.0 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.

CSS Optimization

-7%

Potential reduce by 5.3 kB

  • Original 72.0 kB
  • After minification 71.5 kB
  • After compression 66.7 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. Lugex.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 49 (62%)

Requests Now

79

After Optimization

30

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

Accessibility Review

lugex.com accessibility score

95

Accessibility Issues

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

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

lugex.com best practices score

83

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

SEO Factors

lugex.com SEO score

83

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

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

    EN

  • Encoding

    UTF-8

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

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