Report Summary

  • 64

    Performance

    Renders faster than
    78% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 42

    Best Practices

    More advanced features
    available than in
    18% of websites

  • 50

    SEO

    Google-friendlier than
    18% of websites

frant.bg

Frant | Spring/Summer 2015 Collection

Page Load Speed

1.1 sec in total

First Response

525 ms

Resources Loaded

526 ms

Page Rendered

0 ms

frant.bg screenshot

About Website

Visit frant.bg now to see the best up-to-date Frant content and also check out these interesting facts you probably never knew about frant.bg

Visit frant.bg

Key Findings

We analyzed Frant.bg page load time and found that the first response time was 525 ms and then it took 526 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

frant.bg performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value4.9 s

66/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.5 s

83/100

10%

Network Requests Diagram

frant.bg

525 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Frant.bg and no external sources were called. The less responsive or slowest element that took the longest time to load (525 ms) belongs to the original domain Frant.bg.

Page Optimization Overview & Recommendations

Page size can be reduced by 210 B (33%)

Content Size

635 B

After Optimization

425 B

In fact, the total size of Frant.bg main page is 635 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 635 B which makes up the majority of the site volume.

HTML Optimization

-33%

Potential reduce by 210 B

  • Original 635 B
  • After minification 633 B
  • After compression 425 B

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 210 B or 33% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

frant.bg accessibility score

54

Accessibility Issues

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

Best Practices

frant.bg best practices score

42

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

frant.bg SEO score

50

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Frant.bg can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Frant.bg 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 Frant. 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: