Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

getwidget.dev

Open Source Flutter UI Library to Ease Your Flutter App Development - Getwidget

Page Load Speed

247 ms in total

First Response

54 ms

Resources Loaded

128 ms

Page Rendered

65 ms

getwidget.dev screenshot

About Website

Click here to check amazing Getwidget content for India. Otherwise, check out these important facts you probably never knew about getwidget.dev

GetWidget is an open source flutter UI library that comes with pre-build 1000+ UI widgets like Flutter button ,Card , Avatar , Alert, Tab & Many more.

Visit getwidget.dev

Key Findings

We analyzed Getwidget.dev page load time and found that the first response time was 54 ms and then it took 193 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 Getwidget.dev rating and web reputation

Performance Metrics

getwidget.dev performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value5.3 s

21/100

25%

SI (Speed Index)

Value5.3 s

57/100

10%

TBT (Total Blocking Time)

Value2,360 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.06

98/100

15%

TTI (Time to Interactive)

Value14.0 s

10/100

10%

Network Requests Diagram

getwidget.dev

54 ms

main.css

5 ms

beacon.js

45 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

47 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that 50% of them (2 requests) were addressed to the original Getwidget.dev, 25% (1 request) were made to Performance.radar.cloudflare.com and 25% (1 request) were made to Static.cloudflareinsights.com. The less responsive or slowest element that took the longest time to load (54 ms) belongs to the original domain Getwidget.dev.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.8 kB (46%)

Content Size

8.1 kB

After Optimization

4.4 kB

In fact, the total size of Getwidget.dev main page is 8.1 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. HTML takes 5.9 kB which makes up the majority of the site volume.

HTML Optimization

-63%

Potential reduce by 3.7 kB

  • Original 5.9 kB
  • After minification 5.6 kB
  • After compression 2.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 3.7 kB or 63% of the original size.

CSS Optimization

-1%

Potential reduce by 13 B

  • Original 2.2 kB
  • After minification 2.2 kB
  • After compression 2.2 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. Getwidget.dev has all CSS files already compressed.

Requests Breakdown

We found no issues to fix!

Requests Now

1

After Optimization

1

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Getwidget. According to our analytics all requests are already optimized.

Accessibility Review

getwidget.dev accessibility score

72

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

[role]s are not contained by their required parent element

High

ARIA IDs are not unique

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

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

getwidget.dev 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

getwidget.dev SEO score

86

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 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 Getwidget.dev 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 Getwidget.dev 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 Getwidget. 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: