Tools & Wizards About Us
fultoo.in screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 100

    SEO

    Google-friendlier than
    95% of websites

fultoo.in

FulToo - Don't Think. Just Go. - Outsource your Weekend Plans

Page Load Speed

2.6 sec in total

First Response

335 ms

Resources Loaded

1.8 sec

Page Rendered

472 ms

fultoo.in screenshot

About Website

Welcome to fultoo.in homepage info - get ready to check Ful Too best content right away, or after learning these important things about fultoo.in

FulToo is a weekend planning service that encourages individuals to embrace the uncertain. Get ready to think less and do more!

Visit fultoo.in

Key Findings

We analyzed Fultoo.in page load time and found that the first response time was 335 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.

Performance Metrics

fultoo.in performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.7 s

92/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value4,080 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.117

85/100

15%

TTI (Time to Interactive)

Value7.8 s

45/100

10%

Network Requests Diagram

fultoo.in

335 ms

vendor-styles.css

33 ms

styles.css

32 ms

site.css

195 ms

js

97 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 30% of them (8 requests) were addressed to the original Fultoo.in, 15% (4 requests) were made to Google-analytics.com and 15% (4 requests) were made to S3.amazonaws.com. The less responsive or slowest element that took the longest time to load (557 ms) relates to the external source S3.amazonaws.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 66.2 kB (6%)

Content Size

1.2 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fultoo.in main page is 1.2 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 921.4 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 28.3 kB

  • Original 35.1 kB
  • After minification 34.1 kB
  • After compression 6.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 28.3 kB or 81% of the original size.

Image Optimization

-0%

Potential reduce by 4.2 kB

  • Original 921.4 kB
  • After minification 917.2 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. Ful Too images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 32.1 kB

  • Original 179.9 kB
  • After minification 179.9 kB
  • After compression 147.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 32.1 kB or 18% of the original size.

CSS Optimization

-7%

Potential reduce by 1.6 kB

  • Original 22.6 kB
  • After minification 22.6 kB
  • After compression 21.0 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. Fultoo.in has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 12 (52%)

Requests Now

23

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fultoo.in

fultoo.in

335 ms

vendor-styles.css

vendor-styles.css

33 ms

styles.css

styles.css

32 ms

site.css

site.css

195 ms

js

js

97 ms

jquery.min.js

jquery.min.js

76 ms

vendor-scripts.min.js

vendor-scripts.min.js

50 ms

scripts.min.js

scripts.min.js

46 ms

lr-site.js

lr-site.js

48 ms

css

css

23 ms

css

css

35 ms

css

css

36 ms

analytics.js

analytics.js

457 ms

loading.gif

loading.gif

114 ms

2qalq5-fultoo-logo-red-small-2.png

2qalq5-fultoo-logo-red-small-2.png

539 ms

75kb6h-button_get-started-black.png

75kb6h-button_get-started-black.png

557 ms

analytics.js

analytics.js

369 ms

piwik.js

piwik.js

439 ms

y0as7i-vishnu-r-nair-639172-unsplash.jpg

y0as7i-vishnu-r-nair-639172-unsplash.jpg

186 ms

nscnhx-danielle-macinnes-222441-unsplash.png

nscnhx-danielle-macinnes-222441-unsplash.png

231 ms

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e2fwniDhzA.ttf

7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e2fwniDhzA.ttf

123 ms

wEO_EBrAnc9BLjLQAUk1VvoP_kgXiQ.ttf

wEO_EBrAnc9BLjLQAUk1VvoP_kgXiQ.ttf

185 ms

m8JVjfNVeKWVnh3QMuKkFcZVaUuC99GUDg.ttf

m8JVjfNVeKWVnh3QMuKkFcZVaUuC99GUDg.ttf

294 ms

collect

collect

84 ms

collect

collect

103 ms

collect

collect

33 ms

ga-audiences

ga-audiences

60 ms

Accessibility Review

fultoo.in accessibility score

92

Accessibility Issues

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

fultoo.in best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

SEO Factors

fultoo.in SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fultoo.in 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 Fultoo.in 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

fultoo.in

Open Graph data is detected on the main page of Ful Too. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: