Tools & Wizards About Us
resources.longines.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

resources.longines.com

Longines® Watches Official e-shop in the United States

Page Load Speed

21.6 sec in total

First Response

1.1 sec

Resources Loaded

19.7 sec

Page Rendered

899 ms

resources.longines.com screenshot

About Website

Welcome to resources.longines.com homepage info - get ready to check Resources Longines best content for United States right away, or after learning these important things about resources.longines.com

Browse our collections of Swiss watches and discover Longines' expertise, built on tradition, elegance and performance since 1832

Visit resources.longines.com

Key Findings

We analyzed Resources.longines.com page load time and found that the first response time was 1.1 sec and then it took 20.6 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.

Performance Metrics

resources.longines.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

81/100

10%

LCP (Largest Contentful Paint)

Value11.0 s

0/100

25%

SI (Speed Index)

Value12.7 s

3/100

10%

TBT (Total Blocking Time)

Value4,720 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.058

98/100

15%

TTI (Time to Interactive)

Value24.8 s

0/100

10%

Network Requests Diagram

1061 ms

styles-m.min.css

1057 ms

styles-l.min.css

3070 ms

require.min.js

2115 ms

requirejs-min-resolver.min.js

2088 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Resources.longines.com, 7% (3 requests) were made to Connect.facebook.net and 5% (2 requests) were made to Static.scarabresearch.com. The less responsive or slowest element that took the longest time to load (7.2 sec) relates to the external source Longines.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (54%)

Content Size

1.9 MB

After Optimization

869.4 kB

  • JavaScript
  • CSS

In fact, the total size of Resources.longines.com main page is 1.9 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. 55% of websites need less resources to load. Javascripts take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-0%

Potential reduce by -8 B

  • Original 0 B

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 web page is already compressed.

JavaScript Optimization

-49%

Potential reduce by 794.5 kB

  • Original 1.6 MB
  • After minification 1.6 MB
  • After compression 823.2 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 794.5 kB or 49% of the original size.

CSS Optimization

-82%

Potential reduce by 212.0 kB

  • Original 258.3 kB
  • After minification 258.1 kB
  • After compression 46.3 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. Resources.longines.com needs all CSS files to be minified and compressed as it can save up to 212.0 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

31

After Optimization

6

  • AJAX
  • JavaScript
  • CSS

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

Network Requests Diagram

1061 ms

styles-m.min.css

styles-m.min.css

1057 ms

styles-l.min.css

styles-l.min.css

3070 ms

require.min.js

require.min.js

2115 ms

requirejs-min-resolver.min.js

requirejs-min-resolver.min.js

2088 ms

baseUrlResolver.min.js

baseUrlResolver.min.js

3231 ms

requirejs-map.min.js

requirejs-map.min.js

2076 ms

bundle0.min.js

bundle0.min.js

4096 ms

bundle1.min.js

bundle1.min.js

4135 ms

bundle2.min.js

bundle2.min.js

5161 ms

bundle3.min.js

bundle3.min.js

3237 ms

bundle4.min.js

bundle4.min.js

4143 ms

bundle5.min.js

bundle5.min.js

4138 ms

bundle6.min.js

bundle6.min.js

6300 ms

bundle7.min.js

bundle7.min.js

7119 ms

static.min.js

static.min.js

6161 ms

mixins.min.js

mixins.min.js

6190 ms

requirejs-config.min.js

requirejs-config.min.js

5182 ms

lazysizes-custom.min.js

lazysizes-custom.min.js

7182 ms

kameleoon.js

kameleoon.js

61 ms

emarsys-m2-email-after-233.js

emarsys-m2-email-after-233.js

37 ms

ZKVZT-M68SD-2HRLL-F8GLR-PZA6F

ZKVZT-M68SD-2HRLL-F8GLR-PZA6F

149 ms

LonginesSansRegular.woff

LonginesSansRegular.woff

3175 ms

LonginesSansLight.woff

LonginesSansLight.woff

4087 ms

LonginesSansMedium.woff

LonginesSansMedium.woff

4109 ms

LonginesSansBold.woff

LonginesSansBold.woff

6284 ms

icomoon.woff

icomoon.woff

4298 ms

LonginesSerifHeadline-Regular.woff

LonginesSerifHeadline-Regular.woff

7003 ms

config.json

config.json

45 ms

fbevents.js

fbevents.js

30 ms

scarab-v2.js

scarab-v2.js

128 ms

identity.js

identity.js

60 ms

156701311665986

156701311665986

188 ms

ko.min.js

ko.min.js

1759 ms

uiRegistry.min.js

uiRegistry.min.js

4807 ms

jquery-storageapi.min.js

jquery-storageapi.min.js

4213 ms

picturefill.min.js

picturefill.min.js

2186 ms

pageAnims.min.js

pageAnims.min.js

5436 ms

wploader.js

wploader.js

17 ms

wpes5.js

wpes5.js

4 ms

kameleoon-iframe.html

kameleoon-iframe.html

2029 ms

print.min.css

print.min.css

3024 ms

nr-1216.min.js

nr-1216.min.js

22 ms

Accessibility Review

resources.longines.com accessibility score

92

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

Links do not have a discernible name

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

resources.longines.com 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

High

Missing source maps for large first-party JavaScript

SEO Factors

resources.longines.com SEO score

77

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

Content Best Practices

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

Impact

Issue

High

Document doesn't have a valid hreflang

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Resources.longines.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Resources.longines.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

resources.longines.com

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