Tools & Wizards About Us
raymondweil.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

raymondweil.com

RAYMOND WEIL Official Website - Luxury Swiss Watches

Page Load Speed

3.8 sec in total

First Response

844 ms

Resources Loaded

2.6 sec

Page Rendered

433 ms

raymondweil.com screenshot

About Website

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

Discover Swiss-made horology at its finest from one of the last family-owned luxury watchmaking brands in the world. Browse our elegant and refined timepieces inspired by music and the arts.

Visit raymondweil.com

Key Findings

We analyzed Raymondweil.com page load time and found that the first response time was 844 ms and then it took 3 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

raymondweil.com performance score

0

Network Requests Diagram

844 ms

jquery.js

80 ms

jquery.ui.js

95 ms

css

25 ms

utils2.css

72 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Raymondweil.com, 7% (4 requests) were made to Fonts.gstatic.com and 4% (2 requests) were made to Raymond-weil.com. The less responsive or slowest element that took the longest time to load (844 ms) relates to the external source Raymond-weil.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 687.5 kB (21%)

Content Size

3.2 MB

After Optimization

2.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Raymondweil.com main page is 3.2 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. 50% of websites need less resources to load. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 34.7 kB

  • Original 45.5 kB
  • After minification 43.7 kB
  • After compression 10.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. 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 34.7 kB or 76% of the original size.

Image Optimization

-11%

Potential reduce by 295.1 kB

  • Original 2.6 MB
  • After minification 2.4 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. Obviously, RAYMOND WEIL needs image optimization as it can save up to 295.1 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

-63%

Potential reduce by 284.5 kB

  • Original 454.6 kB
  • After minification 454.4 kB
  • After compression 170.1 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 284.5 kB or 63% of the original size.

CSS Optimization

-85%

Potential reduce by 73.2 kB

  • Original 86.3 kB
  • After minification 73.5 kB
  • After compression 13.1 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. Raymondweil.com needs all CSS files to be minified and compressed as it can save up to 73.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (56%)

Requests Now

48

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 48 CSS, Javascripts, AJAX and image requests in order to completely render the main page of RAYMOND WEIL. 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 as a result speed up the page load time.

Network Requests Diagram

844 ms

jquery.js

jquery.js

80 ms

jquery.ui.js

jquery.ui.js

95 ms

css

css

25 ms

utils2.css

utils2.css

72 ms

main2.css

main2.css

75 ms

matchMedia.js

matchMedia.js

121 ms

utils2.js

utils2.js

93 ms

main.js

main.js

65 ms

conversion.js

conversion.js

18 ms

analytics.js

analytics.js

139 ms

fbds.js

fbds.js

137 ms

earth.png

earth.png

136 ms

o2.eyereturn.com

o2.eyereturn.com

81 ms

mobile_menu.png

mobile_menu.png

57 ms

logo.png

logo.png

56 ms

mobile_my_account.png

mobile_my_account.png

56 ms

nav_picto.png

nav_picto.png

55 ms

btn.png

btn.png

55 ms

Beatles-1920x860_slider_home_6.jpg

Beatles-1920x860_slider_home_6.jpg

110 ms

Beatles-1280x650_slider_home_mobile_1.jpg

Beatles-1280x650_slider_home_mobile_1.jpg

104 ms

UMG-1920x860_slider_home_1.jpg

UMG-1920x860_slider_home_1.jpg

163 ms

KW_banner_1920x860px_e_72dpi.jpg

KW_banner_1920x860px_e_72dpi.jpg

152 ms

skeleton-1920x860_slider_home.jpg

skeleton-1920x860_slider_home.jpg

130 ms

slider-sprite.png

slider-sprite.png

90 ms

diamond_pattern.jpg

diamond_pattern.jpg

110 ms

e4f48c63822aa13a61a1674c873cc8f3_f2576.png

e4f48c63822aa13a61a1674c873cc8f3_f2576.png

152 ms

e2b2c9d6742b46a9af4b33ce0e47ea51_f2574.png

e2b2c9d6742b46a9af4b33ce0e47ea51_f2574.png

166 ms

783d06bc413478ea4202a37f5ae736de_f2586.png

783d06bc413478ea4202a37f5ae736de_f2586.png

149 ms

Home_Bloc3_StoreLocator_2.png

Home_Bloc3_StoreLocator_2.png

145 ms

Home_CTA_Register_2.jpg

Home_CTA_Register_2.jpg

158 ms

footer.png

footer.png

166 ms

sep.gif

sep.gif

156 ms

social_btn.png

social_btn.png

155 ms

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

47 ms

toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf

toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf

64 ms

toadOcfmlt9b38dHJxOBGEMbjGELOEJD5J8DUmxkO-A.ttf

toadOcfmlt9b38dHJxOBGEMbjGELOEJD5J8DUmxkO-A.ttf

84 ms

toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf

toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf

84 ms

collect

collect

10 ms

collect

collect

111 ms

72 ms

67 ms

cminit2

cminit2

79 ms

firstevent

firstevent

29 ms

71 ms

Pug

Pug

43 ms

rum

rum

57 ms

61 ms

sync

sync

17 ms

tap.php

tap.php

16 ms

rum

rum

18 ms

pixel.gif

pixel.gif

7 ms

18 ms

mapuser

mapuser

5 ms

roundtrip.js

roundtrip.js

32 ms

2 ms

SEO Factors

raymondweil.com SEO score

0

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 Raymondweil.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 Raymondweil.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

raymondweil.com

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