5 sec in total
1.5 sec
3.3 sec
209 ms
Click here to check amazing LAGFF content for United States. Otherwise, check out these important facts you probably never knew about lagff.org
Against all odds, we are busy planning our return to the theaters! While keeping Covid-19 precautions, we will open the doors to the public once again, with limited in-person screenings and events, Ma...
Visit lagff.orgWe analyzed Lagff.org page load time and found that the first response time was 1.5 sec and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
lagff.org performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value9.0 s
1/100
25%
Value29.8 s
0/100
10%
Value16,580 ms
0/100
30%
Value0.234
53/100
15%
Value31.3 s
0/100
10%
1477 ms
151 ms
114 ms
114 ms
111 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 78% of them (49 requests) were addressed to the original Lagff.org, 6% (4 requests) were made to F.vimeocdn.com and 5% (3 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Lagff.org.
Page size can be reduced by 366.5 kB (72%)
512.5 kB
146.0 kB
In fact, the total size of Lagff.org main page is 512.5 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. 60% of websites need less resources to load. Javascripts take 356.6 kB which makes up the majority of the site volume.
Potential reduce by 30.8 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 30.8 kB or 79% of the original size.
Potential reduce by 231.8 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 231.8 kB or 65% of the original size.
Potential reduce by 103.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. Lagff.org needs all CSS files to be minified and compressed as it can save up to 103.9 kB or 89% of the original size.
Number of requests can be reduced by 29 (48%)
61
32
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LAGFF. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
lagff.org
1477 ms
style.css
151 ms
prettyPhoto.css
114 ms
shadowbox.css
114 ms
extras.css
111 ms
styles.css
114 ms
swfobject.js
121 ms
jquery.js
303 ms
jquery-migrate.min.js
175 ms
jquery.form.min.js
168 ms
jquery.corner.js
167 ms
cufon-yui.js
172 ms
TitilliumText14L_300.font.js
242 ms
superfish.js
219 ms
jquery.prettyPhoto.js
232 ms
jquery.validate.min.js
230 ms
init-square.js
232 ms
form_init.js
250 ms
fa526a2a117afd39f06dd9b70460cf3c.js
320 ms
scripts.js
258 ms
wp-embed.min.js
258 ms
wp-emoji-release.min.js
190 ms
ga.js
25 ms
144574878
165 ms
LAGFFBG.jpg
485 ms
lagff_logo_home.png
121 ms
menu_bg.png
122 ms
CN-lagff-7june2015-363-IPDF.jpg
351 ms
2015_winner_stratos.jpg
164 ms
2015_winner_agora.jpg
212 ms
2015_winner_citizen.jpg
316 ms
2015_winner_family.jpg
350 ms
2015_winner_olive.jpg
319 ms
2015_winner_portrait.jpg
315 ms
nb.png
349 ms
orpheus_homeimage.jpg
348 ms
projectdiscoveryforun.jpg
371 ms
lagff_homepage_gallery2015.jpg
408 ms
2015goldpasssmall.jpg
403 ms
lagff2015lineup_small.jpg
402 ms
lagff_ipdf_industry_small.jpg
400 ms
hostess_logo.jpg
431 ms
twitter_bird.png
459 ms
facebook.jpg
461 ms
twitter.jpg
458 ms
youtube.jpg
462 ms
hostagreek.jpg
481 ms
bg.gif
518 ms
top3arrow.png
520 ms
top1arrow.png
522 ms
nb.png
1527 ms
__utm.gif
12 ms
127784140
65 ms
player.js
101 ms
player.css
80 ms
ga.js
54 ms
vuid.min.js
97 ms
__utm.gif
17 ms
__utm.gif
28 ms
proxy.html
35 ms
518682376.jpg
95 ms
7211194_60x60.jpg
67 ms
542443633.jpg
69 ms
lagff.org accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
No form fields have multiple labels
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
lagff.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
lagff.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lagff.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Lagff.org 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.
lagff.org
Open Graph description is not detected on the main page of LAGFF. 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: