Tools & Wizards About Us
franrive.com screenshot

Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

franrive.com

Franrive S.L. Empresa de Representaciones y Gestion de Fabricantes y sus Marcas en Canarias.

Page Load Speed

6.2 sec in total

First Response

2.2 sec

Resources Loaded

3.9 sec

Page Rendered

193 ms

franrive.com screenshot

About Website

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

Desde 1997 una empresa especializada en la Gestion Integral con Representacion en Esclusiva de los Fabricantes y sus Marcas en todas las Islas Canarias.

Visit franrive.com

Key Findings

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

Performance Metrics

franrive.com performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.1 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value110 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.165

71/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

franrive.com

2164 ms

wp-emoji-release.min.js

229 ms

bootstrap.css

590 ms

shortcodes.css

255 ms

styles.css

233 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 82% of them (58 requests) were addressed to the original Franrive.com, 13% (9 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Franrive.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (70%)

Content Size

2.6 MB

After Optimization

761.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 84.7 kB

  • Original 103.3 kB
  • After minification 100.2 kB
  • After compression 18.6 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 84.7 kB or 82% of the original size.

Image Optimization

-9%

Potential reduce by 35.5 kB

  • Original 396.6 kB
  • After minification 361.2 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. Franrive images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 744.4 kB

  • Original 986.9 kB
  • After minification 836.5 kB
  • After compression 242.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 744.4 kB or 75% of the original size.

CSS Optimization

-87%

Potential reduce by 937.1 kB

  • Original 1.1 MB
  • After minification 942.4 kB
  • After compression 139.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. Franrive.com needs all CSS files to be minified and compressed as it can save up to 937.1 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (73%)

Requests Now

56

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

franrive.com

franrive.com

2164 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

229 ms

bootstrap.css

bootstrap.css

590 ms

shortcodes.css

shortcodes.css

255 ms

styles.css

styles.css

233 ms

mediaelementplayer.min.css

mediaelementplayer.min.css

366 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

338 ms

rgs.css

rgs.css

352 ms

font-awesome.min.css

font-awesome.min.css

483 ms

style.css

style.css

906 ms

prettyPhoto.css

prettyPhoto.css

449 ms

responsive.css

responsive.css

835 ms

css

css

37 ms

ascend.css

ascend.css

505 ms

js_composer.min.css

js_composer.min.css

1127 ms

franrive.com

franrive.com

802 ms

css

css

28 ms

gdpr-main.css

gdpr-main.css

774 ms

jquery.js

jquery.js

843 ms

jquery-migrate.min.js

jquery-migrate.min.js

899 ms

bootstrap.js

bootstrap.js

937 ms

init.js

init.js

951 ms

modernizr.js

modernizr.js

965 ms

ProgressCircle.min.js

ProgressCircle.min.js

1024 ms

jquery.vc_chart.min.js

jquery.vc_chart.min.js

950 ms

core.min.js

core.min.js

844 ms

widget.min.js

widget.min.js

885 ms

position.min.js

position.min.js

900 ms

menu.min.js

menu.min.js

1022 ms

wp-a11y.min.js

wp-a11y.min.js

1025 ms

autocomplete.min.js

autocomplete.min.js

1023 ms

wpss-search-suggest.js

wpss-search-suggest.js

1024 ms

jquery.form.min.js

jquery.form.min.js

1024 ms

scripts.js

scripts.js

1101 ms

prettyPhoto.js

prettyPhoto.js

1101 ms

superfish.js

superfish.js

1102 ms

init.js

init.js

1603 ms

infinitescroll.js

infinitescroll.js

1157 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

1126 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

1154 ms

main.js

main.js

1129 ms

wp-embed.min.js

wp-embed.min.js

1092 ms

js_composer_front.min.js

js_composer_front.min.js

1137 ms

logo-franrive-canarias-alt.png

logo-franrive-canarias-alt.png

261 ms

islas-canarias-francisco-rivero.png

islas-canarias-francisco-rivero.png

531 ms

logo-helios-sf.png

logo-helios-sf.png

294 ms

logo-palacio-de-oriente-sf.png

logo-palacio-de-oriente-sf.png

298 ms

logo-nomen-sf.png

logo-nomen-sf.png

375 ms

logo-borges-sf.png

logo-borges-sf.png

394 ms

logo-oleoestepa-sf.png

logo-oleoestepa-sf.png

412 ms

logo-ubago-sf.png

logo-ubago-sf.png

416 ms

logo-bajamar-sf.png

logo-bajamar-sf.png

491 ms

logo-coreysa-sf.png

logo-coreysa-sf.png

519 ms

logo-pamex-sf.png

logo-pamex-sf.png

527 ms

gdpr-logo.png

gdpr-logo.png

532 ms

analytics.js

analytics.js

91 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

29 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

30 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

73 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

73 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

73 ms

icomoon.woff

icomoon.woff

697 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

73 ms

OpenSans-Regular-webfont.woff

OpenSans-Regular-webfont.woff

707 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

73 ms

OpenSans-Light-webfont.woff

OpenSans-Light-webfont.woff

706 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

82 ms

OpenSans-Semibold-webfont.woff

OpenSans-Semibold-webfont.woff

707 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

82 ms

OpenSansBold-webfont.woff

OpenSansBold-webfont.woff

722 ms

collect

collect

34 ms

Accessibility Review

franrive.com accessibility score

88

Accessibility Issues

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.

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

franrive.com best practices score

83

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

SEO Factors

franrive.com SEO score

93

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

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

franrive.com

Open Graph data is detected on the main page of Franrive. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: