Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 61

    SEO

    Google-friendlier than
    23% of websites

fraglider.pt

Fraglíder - Homepage - Fraglíder

Page Load Speed

2.1 sec in total

First Response

532 ms

Resources Loaded

1.5 sec

Page Rendered

61 ms

fraglider.pt screenshot

About Website

Welcome to fraglider.pt homepage info - get ready to check Fraglider best content for Portugal right away, or after learning these important things about fraglider.pt

Visit fraglider.pt

Key Findings

We analyzed Fraglider.pt page load time and found that the first response time was 532 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

fraglider.pt performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.8 s

27/100

10%

LCP (Largest Contentful Paint)

Value4.3 s

42/100

25%

SI (Speed Index)

Value4.0 s

80/100

10%

TBT (Total Blocking Time)

Value380 ms

69/100

30%

CLS (Cumulative Layout Shift)

Value0.042

99/100

15%

TTI (Time to Interactive)

Value5.9 s

65/100

10%

Network Requests Diagram

fraglider.pt

532 ms

gtm.js

57 ms

uc.js

38 ms

js

47 ms

page.js

12 ms

Our browser made a total of 28 requests to load all elements on the main page. We found that 64% of them (18 requests) were addressed to the original Fraglider.pt, 7% (2 requests) were made to Googletagmanager.com and 7% (2 requests) were made to Static.addtoany.com. The less responsive or slowest element that took the longest time to load (532 ms) belongs to the original domain Fraglider.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 23.5 kB (37%)

Content Size

63.1 kB

After Optimization

39.6 kB

In fact, the total size of Fraglider.pt main page is 63.1 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. 25% of websites need less resources to load. HTML takes 30.6 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 22.4 kB

  • Original 30.6 kB
  • After minification 30.6 kB
  • After compression 8.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 22.4 kB or 73% of the original size.

Image Optimization

-26%

Potential reduce by 898 B

  • Original 3.5 kB
  • After minification 2.6 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, Fraglider needs image optimization as it can save up to 898 B or 26% 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 268 B

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

Requests Breakdown

Number of requests can be reduced by 14 (64%)

Requests Now

22

After Optimization

8

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

Accessibility Review

fraglider.pt accessibility score

88

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

fraglider.pt best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

fraglider.pt SEO score

61

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

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    PT

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fraglider.pt can be misinterpreted by Google and other search engines. Our service has detected that Portuguese is used on the page, and it matches the claimed language. Our system also found out that Fraglider.pt 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 Fraglider. 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: