Access frojo.com. Frojo - Horlogerie et joaillerie depuis 1854

name

value

score

weighting

FCP (First Contentful Paint)

Value26.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value42.4 s

0/100

25%

SI (Speed Index)

Value39.5 s

0/100

10%

TBT (Total Blocking Time)

Value17,380 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.381

27/100

15%

TTI (Time to Interactive)

Value58.4 s

0/100

10%

frojo.com

457 ms

www.frojo.com

986 ms

theme.css

49 ms

relatedproducts-theme.css

431 ms

relatedproducts-global.css

530 ms

Our browser made a total of 112 requests to load all elements on the main page. We found that 63% of them (71 requests) were addressed to the original Frojo.com, 6% (7 requests) were made to Static.rolex.com and 6% (7 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (4.8 sec) belongs to the original domain Frojo.com.

Content Size

1.2 MB

After Optimization

575.1 kB

In fact, the total size of Frojo.com main page is 1.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. 80% 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. CSS take 513.4 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 196.0 kB

Original 226.1 kB
After minification 179.7 kB
After compression 30.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. This page needs HTML code to be minified as it can gain 46.5 kB, which is 21% 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 196.0 kB or 87% of the original size.

Image Optimization

-0%

Potential reduce by 19 B

Original 313.6 kB
After minification 313.6 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. Frojo images are well optimized though.

JavaScript Optimization

-45%

Potential reduce by 45.4 kB

Original 100.9 kB
After minification 100.7 kB
After compression 55.5 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 45.4 kB or 45% of the original size.

CSS Optimization

-66%

Potential reduce by 337.5 kB

Original 513.4 kB
After minification 509.5 kB
After compression 175.9 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. Frojo.com needs all CSS files to be minified and compressed as it can save up to 337.5 kB or 66% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

FR
Language Claimed

FR
Encoding

UTF-8

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

frojo.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Frojo - Horlogerie et joaillerie depuis 1854

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

frojo.com

www.frojo.com

theme.css

relatedproducts-theme.css

relatedproducts-global.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

frojo.com

www.frojo.com

theme.css

relatedproducts-theme.css

relatedproducts-global.css

relatedproducts-column.css

app.min.css

paypal_fo.css

leoblog.css

megamenu.css

leomenusidebar.css

jquery.mCustomScrollbar.css

front.css

advancedpopup-front.css

jquery.fancybox-transitions.css

front-v3.5.0.css

front.css

front.css

front.css

front.css

jquery.fancybox.css

leosearch.css

jquery.autocomplete_productsearch.css

custom.css

owl.carousel.css

owl.theme.css

slick-theme.css

slick.css

styles.css

unique.css

css

Lb8X-sSUKWM

rocket-loader.min.js

logo_signature.svg

close.png

menu_horlo.jpg

menu_joaillerie.jpg

menu_frojo.webp

rolex_sept22_desk.webp

frojo_desk.webp

breitling-hp-desk.webp

omega-seamaster-noir-desk.webp

2560x2048-PASHA-STEEL-WSPA0013-desk.webp