Tools & Wizards About Us
franko.su screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

franko.su

Профессиональные кофемашины – официальный дистрибьютор кофемашин Franke в интернет магазине ФРАНКО

Page Load Speed

4.6 sec in total

First Response

747 ms

Resources Loaded

3.6 sec

Page Rendered

281 ms

franko.su screenshot

About Website

Welcome to franko.su homepage info - get ready to check Franko best content for Russia right away, or after learning these important things about franko.su

Продажа профессиональных кофемашин от «ФРАНКО» в Москве, Санкт-Петербурге, Екатеринбурге, Казани, Краснодаре и Новосибирске. Практичные кофемашины для любой цели и любого заведения от официального дис...

Visit franko.su

Key Findings

We analyzed Franko.su page load time and found that the first response time was 747 ms and then it took 3.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

franko.su performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value3.5 s

64/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0.014

100/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

franko.su

747 ms

site.css

649 ms

top-logo.png

476 ms

1-0-slide-cafe-1.jpg

610 ms

slider-logo-franke-1.gif

340 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 85% of them (40 requests) were addressed to the original Franko.su, 9% (4 requests) were made to Google-analytics.com and 4% (2 requests) were made to Counter.yadro.ru. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Franko.su.

Page Optimization Overview & Recommendations

Page size can be reduced by 291.9 kB (33%)

Content Size

894.8 kB

After Optimization

602.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Franko.su main page is 894.8 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. 30% of websites need less resources to load. Images take 512.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 32.4 kB

  • Original 41.0 kB
  • After minification 36.1 kB
  • After compression 8.5 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 4.8 kB, which is 12% 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 32.4 kB or 79% of the original size.

Image Optimization

-4%

Potential reduce by 20.1 kB

  • Original 512.7 kB
  • After minification 492.7 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. Franko images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 145.6 kB

  • Original 231.5 kB
  • After minification 231.5 kB
  • After compression 85.9 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 145.6 kB or 63% of the original size.

CSS Optimization

-86%

Potential reduce by 93.7 kB

  • Original 109.6 kB
  • After minification 88.6 kB
  • After compression 15.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. Franko.su needs all CSS files to be minified and compressed as it can save up to 93.7 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (8%)

Requests Now

40

After Optimization

37

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

franko.su

franko.su

747 ms

site.css

site.css

649 ms

top-logo.png

top-logo.png

476 ms

1-0-slide-cafe-1.jpg

1-0-slide-cafe-1.jpg

610 ms

slider-logo-franke-1.gif

slider-logo-franke-1.gif

340 ms

LaM.png

LaM.png

342 ms

slider-logo-marco.gif

slider-logo-marco.gif

343 ms

0-slide-rest2-1.jpg

0-slide-rest2-1.jpg

754 ms

0-0-slide-bakery-1.jpg

0-0-slide-bakery-1.jpg

874 ms

0-slide-hotel-1.jpg

0-slide-hotel-1.jpg

872 ms

slide-office2-1.jpg

slide-office2-1.jpg

797 ms

2-slide-gas-station-1.jpg

2-slide-gas-station-1.jpg

794 ms

map.png

map.png

750 ms

brend-franke.jpg

brend-franke.jpg

792 ms

brend-la-marzocco.jpg

brend-la-marzocco.jpg

802 ms

brend-marco1.jpg

brend-marco1.jpg

804 ms

require-jquery.js

require-jquery.js

1132 ms

watch.js

watch.js

33 ms

arrow-list.png

arrow-list.png

440 ms

top-region-moscow.png

top-region-moscow.png

437 ms

top-phone.png

top-phone.png

441 ms

top-search.png

top-search.png

443 ms

mobile-menu.png

mobile-menu.png

441 ms

topmenu-bg-transparent.png

topmenu-bg-transparent.png

540 ms

slider-logo-line.gif

slider-logo-line.gif

539 ms

tabmenu-bg.png

tabmenu-bg.png

558 ms

catalog-hover-l.png

catalog-hover-l.png

575 ms

icon-menu.png

icon-menu.png

577 ms

catalog-hover-r.png

catalog-hover-r.png

678 ms

redlenta-bg.png

redlenta-bg.png

677 ms

catalog-shadow.png

catalog-shadow.png

694 ms

catalog-pic.png

catalog-pic.png

1162 ms

arrow-round.png

arrow-round.png

714 ms

machine-big.png

machine-big.png

857 ms

percent.png

percent.png

812 ms

arrow-red.png

arrow-red.png

811 ms

analytics.js

analytics.js

36 ms

ga.js

ga.js

57 ms

hit

hit

357 ms

OpenSans.woff

OpenSans.woff

945 ms

OpenSans-Bold.woff

OpenSans-Bold.woff

1158 ms

OpenSans-Extrabold.woff

OpenSans-Extrabold.woff

1097 ms

OpenSans-Semibold.woff

OpenSans-Semibold.woff

1295 ms

collect

collect

123 ms

__utm.gif

__utm.gif

49 ms

hit

hit

131 ms

site.js

site.js

1655 ms

Accessibility Review

franko.su accessibility score

73

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

franko.su 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

franko.su SEO score

85

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

    RU

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Franko.su can be misinterpreted by Google and other search engines. Our service has detected that Russian 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 Franko.su 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

franko.su

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