Tools & Wizards About Us

Report Summary

  • 4

    Performance

    Renders faster than
    20% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

frojo.com

Frojo - Horlogerie et joaillerie depuis 1854

Page Load Speed

10.7 sec in total

First Response

457 ms

Resources Loaded

8.9 sec

Page Rendered

1.3 sec

About Website

Click here to check amazing Frojo content. Otherwise, check out these important facts you probably never knew about frojo.com

Depuis 1854, Frojo Marseille est le distributeur officiel de plusieurs grandes marques de montres et de bijoux : Rolex, Cartier, Messika, Tudor, Omega, Breitling, Tag Heuer et bien d'autres à déc...

Visit frojo.com

Key Findings

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

Performance Metrics

frojo.com performance score

4

Measured Metrics

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%

Network Requests Diagram

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.

Page Optimization Overview & Recommendations

Page size can be reduced by 578.9 kB (50%)

Content Size

1.2 MB

After Optimization

575.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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 Breakdown

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

Requests Now

94

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

Accessibility Review

frojo.com accessibility score

88

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

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

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

Best Practices

frojo.com best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

frojo.com SEO score

91

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

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

    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

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: