Tools & Wizards About Us
filaf.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 96

    SEO

    Google-friendlier than
    90% of websites

filaf.com

FILAF / Festival International du Livre d'Art et du Film

Page Load Speed

6.7 sec in total

First Response

274 ms

Resources Loaded

5.4 sec

Page Rendered

1 sec

filaf.com screenshot

About Website

Welcome to filaf.com homepage info - get ready to check FILAF best content right away, or after learning these important things about filaf.com

Le FILAF est un évènement annuel dédié aux livres et aux films sur l’art. Il a lieu chaque année durant la dernière semaine de juin dans le centre historique de Perpignan. Le FILAF a pour objectif de ...

Visit filaf.com

Key Findings

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

Performance Metrics

filaf.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

15/100

10%

LCP (Largest Contentful Paint)

Value8.2 s

2/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value1,560 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value11.0 s

21/100

10%

Network Requests Diagram

filaf.com

274 ms

filaf.tumblr.com

412 ms

pre_tumblelog.js

17 ms

theme.css

74 ms

theme.js

133 ms

Our browser made a total of 43 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Filaf.com, 19% (8 requests) were made to Assets.tumblr.com and 16% (7 requests) were made to 40.media.tumblr.com. The less responsive or slowest element that took the longest time to load (518 ms) relates to the external source 36.media.tumblr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 610.4 kB (19%)

Content Size

3.3 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Filaf.com main page is 3.3 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. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-57%

Potential reduce by 490 B

  • Original 862 B
  • After minification 698 B
  • After compression 372 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. This page needs HTML code to be minified as it can gain 164 B, which is 19% 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 490 B or 57% of the original size.

Image Optimization

-4%

Potential reduce by 93.6 kB

  • Original 2.4 MB
  • After minification 2.3 MB

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. FILAF images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 448.6 kB

  • Original 685.0 kB
  • After minification 685.0 kB
  • After compression 236.4 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 448.6 kB or 65% of the original size.

CSS Optimization

-37%

Potential reduce by 67.8 kB

  • Original 181.4 kB
  • After minification 174.3 kB
  • After compression 113.6 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. Filaf.com needs all CSS files to be minified and compressed as it can save up to 67.8 kB or 37% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (23%)

Requests Now

39

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

filaf.com

filaf.com

274 ms

filaf.tumblr.com

filaf.tumblr.com

412 ms

pre_tumblelog.js

pre_tumblelog.js

17 ms

theme.css

theme.css

74 ms

theme.js

theme.js

133 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

15 ms

stylesheet.css

stylesheet.css

16 ms

index.js

index.js

21 ms

tumblr_nw2elnwdOY1s0sj64o1_500.jpg

tumblr_nw2elnwdOY1s0sj64o1_500.jpg

150 ms

tumblr_nw2elnwdOY1s0sj64o1_1280.jpg

tumblr_nw2elnwdOY1s0sj64o1_1280.jpg

99 ms

tumblr_nvndgtIP1j1s0sj64o1_500.jpg

tumblr_nvndgtIP1j1s0sj64o1_500.jpg

126 ms

false

false

120 ms

false

false

117 ms

tumblr_nmqibrim5v1s0sj64o1_500.jpg

tumblr_nmqibrim5v1s0sj64o1_500.jpg

192 ms

tumblr_nevapsucKZ1s0sj64o1_500.png

tumblr_nevapsucKZ1s0sj64o1_500.png

208 ms

tumblr_nevapsucKZ1s0sj64o1_1280.png

tumblr_nevapsucKZ1s0sj64o1_1280.png

284 ms

tumblr_nnb9u9PZpl1s0sj64o1_1280.jpg

tumblr_nnb9u9PZpl1s0sj64o1_1280.jpg

487 ms

tumblr_nmqibrim5v1s0sj64o1_1280.jpg

tumblr_nmqibrim5v1s0sj64o1_1280.jpg

480 ms

tumblr_nevawa06DI1s0sj64o1_500.jpg

tumblr_nevawa06DI1s0sj64o1_500.jpg

518 ms

logo_filaf.svg

logo_filaf.svg

88 ms

tumblr_inline_npudjjYOjf1rbh7qy_1280.jpg

tumblr_inline_npudjjYOjf1rbh7qy_1280.jpg

87 ms

tumblr_inline_np9zk7Qc5j1rbh7qy_1280.png

tumblr_inline_np9zk7Qc5j1rbh7qy_1280.png

85 ms

tumblr_nnb9u9PZpl1s0sj64o1_500.jpg

tumblr_nnb9u9PZpl1s0sj64o1_500.jpg

85 ms

tumblr_nevawa06DI1s0sj64o1_1280.jpg

tumblr_nevawa06DI1s0sj64o1_1280.jpg

85 ms

impixu

impixu

96 ms

impixu

impixu

49 ms

1sZjBiwAAAswgHqAA==

1sZjBiwAAAswgHqAA==

20 ms

1sZjBiwAAAswgHqAA==

1sZjBiwAAAswgHqAA==

19 ms

jnjeJxjYGbACwAAfQAE

jnjeJxjYGbACwAAfQAE

18 ms

analytics.html

analytics.html

32 ms

login_check.html

login_check.html

27 ms

tumblr_nl35auWOXH1s0sj64o1_540.jpg

tumblr_nl35auWOXH1s0sj64o1_540.jpg

26 ms

tumblr_nl35auWOXH1s0sj64o2_540.jpg

tumblr_nl35auWOXH1s0sj64o2_540.jpg

130 ms

tumblr_nlt8r4P49M1s0sj64o1_540.jpg

tumblr_nlt8r4P49M1s0sj64o1_540.jpg

96 ms

tumblr_nlt8r4P49M1s0sj64o2_540.jpg

tumblr_nlt8r4P49M1s0sj64o2_540.jpg

97 ms

rapid-3.36.js

rapid-3.36.js

37 ms

rapidworker-1.2.js

rapidworker-1.2.js

42 ms

ga.js

ga.js

33 ms

analytics.js

analytics.js

51 ms

cs.js

cs.js

48 ms

yql

yql

169 ms

__utm.gif

__utm.gif

12 ms

cedexis.radar.js

cedexis.radar.js

6 ms

Accessibility Review

filaf.com accessibility score

91

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

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

filaf.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

filaf.com SEO score

96

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

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

filaf.com

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