Report Summary

  • 69

    Performance

    Renders faster than
    81% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

gfn.events

GFN 2023: 21 - 24 June, Warsaw, Poland

Page Load Speed

8.4 sec in total

First Response

1.2 sec

Resources Loaded

6.4 sec

Page Rendered

829 ms

gfn.events screenshot

About Website

Welcome to gfn.events homepage info - get ready to check GFN best content right away, or after learning these important things about gfn.events

The 11th edition of the Global Forum on Nicotine will take place June 21 to 24. Register now!

Visit gfn.events

Key Findings

We analyzed Gfn.events page load time and found that the first response time was 1.2 sec and then it took 7.2 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

gfn.events performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value4.5 s

71/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.031

100/100

15%

TTI (Time to Interactive)

Value2.4 s

99/100

10%

Network Requests Diagram

gfn.events

1223 ms

app.8355e6d202fd4ab4fb44.1f1eb59fec84.css

356 ms

bootstrap-icons.4936adebd50e.css

394 ms

all.min.css

28 ms

cjkcms-front.fbcfc1f6a9f5.css

399 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 64% of them (37 requests) were addressed to the original Gfn.events, 24% (14 requests) were made to Gfn.tv and 5% (3 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (4.7 sec) relates to the external source Gfn.tv.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.3 MB (15%)

Content Size

22.3 MB

After Optimization

19.0 MB

In fact, the total size of Gfn.events main page is 22.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. 60% of websites need less resources to load. Images take 21.9 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 104.9 kB

  • Original 120.7 kB
  • After minification 120.7 kB
  • After compression 15.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 104.9 kB or 87% of the original size.

Image Optimization

-14%

Potential reduce by 3.2 MB

  • Original 21.9 MB
  • After minification 18.7 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. Obviously, GFN needs image optimization as it can save up to 3.2 MB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 112 B

  • Original 148.4 kB
  • After minification 148.4 kB
  • After compression 148.3 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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 1.8 kB

  • Original 98.4 kB
  • After minification 98.3 kB
  • After compression 96.5 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. Gfn.events has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 18 (33%)

Requests Now

54

After Optimization

36

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

Accessibility Review

gfn.events accessibility score

77

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

button, link, and menuitem elements do not have accessible names.

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

High

Links do not have a discernible name

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.

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

gfn.events 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

gfn.events SEO score

86

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gfn.events 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 Gfn.events 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 data is detected on the main page of GFN. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: