Tools & Wizards About Us
fonera.fon.com screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

fonera.fon.com

Fon - Fon: The global WiFi network

Page Load Speed

4.8 sec in total

First Response

1.4 sec

Resources Loaded

3.1 sec

Page Rendered

300 ms

fonera.fon.com screenshot

About Website

Welcome to fonera.fon.com homepage info - get ready to check Fon Era best content for Sri Lanka right away, or after learning these important things about fonera.fon.com

Visit fonera.fon.com

Key Findings

We analyzed Fonera.fon.com page load time and found that the first response time was 1.4 sec and then it took 3.4 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

fonera.fon.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value9.8 s

10/100

10%

TBT (Total Blocking Time)

Value380 ms

70/100

30%

CLS (Cumulative Layout Shift)

Value0.082

94/100

15%

TTI (Time to Interactive)

Value11.1 s

20/100

10%

Network Requests Diagram

fon.com

1399 ms

cookie-law-info-public.css

229 ms

cookie-law-info-gdpr.css

313 ms

styles.css

314 ms

slick.css

239 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Fonera.fon.com, 24% (14 requests) were made to Fonts.gstatic.com and 21% (12 requests) were made to Network.fon.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Fon.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 256.8 kB (20%)

Content Size

1.3 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fonera.fon.com main page is 1.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. 55% of websites need less resources to load. Images take 834.1 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 158.0 kB

  • Original 189.3 kB
  • After minification 185.4 kB
  • After compression 31.2 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 158.0 kB or 83% of the original size.

Image Optimization

-11%

Potential reduce by 90.8 kB

  • Original 834.1 kB
  • After minification 743.4 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. Obviously, Fon Era needs image optimization as it can save up to 90.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 2.1 kB

  • Original 149.6 kB
  • After minification 149.6 kB
  • After compression 147.5 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

-7%

Potential reduce by 6.0 kB

  • Original 90.6 kB
  • After minification 90.1 kB
  • After compression 84.7 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. Fonera.fon.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 22 (56%)

Requests Now

39

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fon.com

fon.com

1399 ms

cookie-law-info-public.css

cookie-law-info-public.css

229 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

313 ms

styles.css

styles.css

314 ms

slick.css

slick.css

239 ms

wpls-public.css

wpls-public.css

238 ms

dashicons.min.css

dashicons.min.css

470 ms

style.css

style.css

308 ms

css

css

59 ms

choices.min.css

choices.min.css

242 ms

style.css

style.css

318 ms

jquery.min.js

jquery.min.js

319 ms

jquery-migrate.min.js

jquery-migrate.min.js

319 ms

cookie-law-info-public.js

cookie-law-info-public.js

315 ms

idle-timer.min.js

idle-timer.min.js

248 ms

custom.js

custom.js

446 ms

fonscripts.js

fonscripts.js

447 ms

scripts.min.js

scripts.min.js

449 ms

common.js

common.js

448 ms

hoverIntent.min.js

hoverIntent.min.js

446 ms

maxmegamenu.js

maxmegamenu.js

447 ms

css

css

24 ms

Wi-fiMonetization-Fon.png

Wi-fiMonetization-Fon.png

658 ms

AF_FON_RGB_white.png

AF_FON_RGB_white.png

128 ms

Logo_fon.png

Logo_fon.png

128 ms

240619_agile-tv_TV-in-living-room_Mockup-Home-ENG-01_L-1-e1718796641329.jpg

240619_agile-tv_TV-in-living-room_Mockup-Home-ENG-01_L-1-e1718796641329.jpg

554 ms

fon_logo2.png

fon_logo2.png

128 ms

wifi-MDM-img.png

wifi-MDM-img.png

649 ms

connectivity-solution-img.png

connectivity-solution-img.png

728 ms

map_partners.jpg

map_partners.jpg

495 ms

Grupo-20.png

Grupo-20.png

614 ms

Grupo-16.png

Grupo-16.png

654 ms

Grupo-17.png

Grupo-17.png

575 ms

Grupo-18.png

Grupo-18.png

653 ms

Grupo-19.png

Grupo-19.png

692 ms

Grupo-21.png

Grupo-21.png

719 ms

analytics.js

analytics.js

64 ms

pfsquaresanspro-medium-webfont.woff

pfsquaresanspro-medium-webfont.woff

599 ms

KFOlCnqEu92Fr1MmSU5fBBc-.woff

KFOlCnqEu92Fr1MmSU5fBBc-.woff

47 ms

KFOlCnqEu92Fr1MmWUlfBBc-.woff

KFOlCnqEu92Fr1MmWUlfBBc-.woff

48 ms

modules.ttf

modules.ttf

168 ms

monarch.ttf

monarch.ttf

100 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

63 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

70 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf

71 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

72 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf

72 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVQ.woff

94 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf

70 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

72 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

94 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVc.ttf

95 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff

95 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVc.ttf

96 ms

pfsquaresanspro-regular-webfont.woff

pfsquaresanspro-regular-webfont.woff

607 ms

collect

collect

53 ms

js

js

77 ms

style.min.css

style.min.css

82 ms

Accessibility Review

fonera.fon.com accessibility score

86

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

Links do not have a discernible name

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

fonera.fon.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

SEO Factors

fonera.fon.com SEO score

85

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

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 Fonera.fon.com 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 Fonera.fon.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

fonera.fon.com

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