Tools & Wizards About Us
joyruz.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

joyruz.com

Relojes Online. Venta de Relojes de Marca. Garantía Oficial.

Page Load Speed

5.8 sec in total

First Response

446 ms

Resources Loaded

5.1 sec

Page Rendered

251 ms

joyruz.com screenshot

About Website

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

Relojes en Joyruz. Venta de relojes Casio, Citizen, Lotus, Festina, Viceroy, Guess, Marck Ecko, Swiss Military, Marea, Kyboe,

Visit joyruz.com

Key Findings

We analyzed Joyruz.com page load time and found that the first response time was 446 ms and then it took 5.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

joyruz.com performance score

0

Network Requests Diagram

joyruz.com

446 ms

www.joyruz.com

1469 ms

311 ms

package-sf.css

415 ms

package-sf.js

709 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 89% of them (59 requests) were addressed to the original Joyruz.com, 5% (3 requests) were made to Google-analytics.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Joyruz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 534.0 kB (62%)

Content Size

858.1 kB

After Optimization

324.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Joyruz.com main page is 858.1 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Javascripts take 433.2 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 43.6 kB

  • Original 52.3 kB
  • After minification 37.2 kB
  • After compression 8.7 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 15.1 kB, which is 29% 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 43.6 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 808 B

  • Original 119.9 kB
  • After minification 119.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. Joyruz images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 282.6 kB

  • Original 433.2 kB
  • After minification 432.6 kB
  • After compression 150.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 282.6 kB or 65% of the original size.

CSS Optimization

-82%

Potential reduce by 206.9 kB

  • Original 252.6 kB
  • After minification 221.2 kB
  • After compression 45.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. Joyruz.com needs all CSS files to be minified and compressed as it can save up to 206.9 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (74%)

Requests Now

61

After Optimization

16

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

joyruz.com

joyruz.com

446 ms

www.joyruz.com

www.joyruz.com

1469 ms

311 ms

package-sf.css

package-sf.css

415 ms

package-sf.js

package-sf.js

709 ms

StorefrontStyle_82.css

StorefrontStyle_82.css

432 ms

css

css

57 ms

style-ie.css

style-ie.css

285 ms

es-ES.js

es-ES.js

278 ms

EUR.js

EUR.js

290 ms

string.js

string.js

271 ms

browser.js

browser.js

288 ms

scope.js

scope.js

456 ms

json.js

json.js

533 ms

base64.js

base64.js

543 ms

inject-sec-token.js

inject-sec-token.js

539 ms

cookie.js

cookie.js

539 ms

storage.js

storage.js

547 ms

button.js

button.js

696 ms

draggable.js

draggable.js

792 ms

resizable.js

resizable.js

786 ms

$pub.js

$pub.js

793 ms

class.js

class.js

797 ms

mime.js

mime.js

799 ms

$dict.js

$dict.js

969 ms

core.js

core.js

1174 ms

support.js

support.js

1065 ms

$tmpl.js

$tmpl.js

1059 ms

load.js

load.js

1067 ms

touch.js

touch.js

1179 ms

version.js

version.js

1237 ms

validate.js

validate.js

1332 ms

de_epages.js

de_epages.js

1335 ms

es_ES.gif

es_ES.gif

1097 ms

bgr_header_floatin.png

bgr_header_floatin.png

1194 ms

bgr_header.png

bgr_header.png

1204 ms

bgr_header_boxbody_floatin.png

bgr_header_boxbody_floatin.png

1263 ms

prueba-para-colgar-en-epages.jpg

prueba-para-colgar-en-epages.jpg

1361 ms

prueba-2-logo-joyruz.jpg

prueba-2-logo-joyruz.jpg

1497 ms

ico_s_basket.png

ico_s_basket.png

1370 ms

bgr_top.png

bgr_top.png

1467 ms

citizen_argyor_regalo_registro_rotativo.gif

citizen_argyor_regalo_registro_rotativo.gif

2331 ms

Citizen_CC1054-56E_m.jpg

Citizen_CC1054-56E_m.jpg

1680 ms

Swiss-military-6518809007_m.jpg

Swiss-military-6518809007_m.jpg

1756 ms

Citizen-AS4020-52E_m.jpg

Citizen-AS4020-52E_m.jpg

1829 ms

VICEROY-47659-58_m.jpg

VICEROY-47659-58_m.jpg

1970 ms

FM.SS.FPH.U.S.11_m.jpg

FM.SS.FPH.U.S.11_m.jpg

1861 ms

ico_s_search.png

ico_s_search.png

1928 ms

gegTSDBDs5le3g6uxU1ZsYB9a16epZVaac-gfobfbfA.ttf

gegTSDBDs5le3g6uxU1ZsYB9a16epZVaac-gfobfbfA.ttf

27 ms

cl6rhMY77Ilk8lB_uYRRwH726VmFjkD_1knHNL407_k.ttf

cl6rhMY77Ilk8lB_uYRRwH726VmFjkD_1knHNL407_k.ttf

28 ms

ga.js

ga.js

12 ms

inpage_linkid.js

inpage_linkid.js

7 ms

__utm.gif

__utm.gif

13 ms

dropdown.js

dropdown.js

1858 ms

$ready.js

$ready.js

1875 ms

suggest.js

suggest.js

1876 ms

energylabel.js

energylabel.js

1965 ms

utf8.js

utf8.js

1986 ms

bgr_content.png

bgr_content.png

2038 ms

img_content_separatorline.png

img_content_separatorline.png

1955 ms

bgr_bottom_floatin.png

bgr_bottom_floatin.png

1864 ms

bgr_bottom.png

bgr_bottom.png

1989 ms

bgr_footer.png

bgr_footer.png

2045 ms

dict.es.json

dict.es.json

2004 ms

dictionary.es.json

dictionary.es.json

467 ms

a.js

a.js

477 ms

SEO Factors

joyruz.com SEO score

0

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

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

joyruz.com

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