Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

geefree.com

Fillo Factory | Quality and Culinary Driven

Page Load Speed

211 ms in total

First Response

53 ms

Resources Loaded

69 ms

Page Rendered

89 ms

geefree.com screenshot

About Website

Click here to check amazing Geefree content. Otherwise, check out these important facts you probably never knew about geefree.com

Beginning with our speciality in fillo doughs, appetizers, desserts and fillo pies – we now make quality small bites in every category.

Visit geefree.com

Key Findings

We analyzed Geefree.com page load time and found that the first response time was 53 ms and then it took 158 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. This domain responded with an error, which can significantly jeopardize Geefree.com rating and web reputation

Performance Metrics

geefree.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value19.0 s

0/100

25%

SI (Speed Index)

Value26.5 s

0/100

10%

TBT (Total Blocking Time)

Value49,400 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.164

72/100

15%

TTI (Time to Interactive)

Value73.3 s

0/100

10%

Network Requests Diagram

geefree.com

53 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Geefree.com and no external sources were called. The less responsive or slowest element that took the longest time to load (53 ms) belongs to the original domain Geefree.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 45 B (33%)

Content Size

138 B

After Optimization

93 B

In fact, the total size of Geefree.com main page is 138 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 138 B which makes up the majority of the site volume.

HTML Optimization

-33%

Potential reduce by 45 B

  • Original 138 B
  • After minification 136 B
  • After compression 93 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. 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 45 B or 33% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

geefree.com accessibility score

81

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

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

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

geefree.com 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

High

Page has valid source maps

SEO Factors

geefree.com SEO score

83

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

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Geefree.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Geefree.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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