Tools & Wizards About Us
widg.it screenshot

Report Summary

  • 36

    Performance

    Renders faster than
    56% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

widg.it

Widgit Software | Widgit Symbols Help Communication

Page Load Speed

8.1 sec in total

First Response

67 ms

Resources Loaded

7.7 sec

Page Rendered

337 ms

widg.it screenshot

About Website

Welcome to widg.it homepage info - get ready to check Widg best content right away, or after learning these important things about widg.it

Widgit Symbols are used worldwide to support people and help them realise their full potential, no matter what their age, ability or background.

Visit widg.it

Key Findings

We analyzed Widg.it page load time and found that the first response time was 67 ms and then it took 8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

widg.it performance score

36

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value920 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.033

100/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

Network Requests Diagram

widg.it

67 ms

widgit.com

44 ms

www.widgit.com

426 ms

widgit-layout.css

387 ms

widgit-design.css

419 ms

Our browser made a total of 109 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Widg.it, 90% (98 requests) were made to Widgit.com and 3% (3 requests) were made to Prong.widgit.com. The less responsive or slowest element that took the longest time to load (2.8 sec) relates to the external source Widgit.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 164.8 kB (15%)

Content Size

1.1 MB

After Optimization

905.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Widg.it main page is 1.1 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 766.0 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 99.5 kB

  • Original 113.2 kB
  • After minification 113.2 kB
  • After compression 13.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 99.5 kB or 88% of the original size.

Image Optimization

-3%

Potential reduce by 24.8 kB

  • Original 766.0 kB
  • After minification 741.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. Widg images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 35.3 kB

  • Original 160.8 kB
  • After minification 160.7 kB
  • After compression 125.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 35.3 kB or 22% of the original size.

CSS Optimization

-17%

Potential reduce by 5.2 kB

  • Original 30.1 kB
  • After minification 29.8 kB
  • After compression 24.9 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. Widg.it needs all CSS files to be minified and compressed as it can save up to 5.2 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 45 (44%)

Requests Now

102

After Optimization

57

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

widg.it

widg.it

67 ms

widgit.com

widgit.com

44 ms

www.widgit.com

www.widgit.com

426 ms

widgit-layout.css

widgit-layout.css

387 ms

widgit-design.css

widgit-design.css

419 ms

widgit-menupage.css

widgit-menupage.css

425 ms

widgit-content.css

widgit-content.css

420 ms

widgit-navigation-and-layout.css

widgit-navigation-and-layout.css

417 ms

shop.css

shop.css

432 ms

font-awesome.min.css

font-awesome.min.css

798 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

921 ms

slick.min.js

slick.min.js

827 ms

intersection-observer.min.js

intersection-observer.min.js

796 ms

animated-gifs.js

animated-gifs.js

822 ms

slick.css

slick.css

806 ms

slick-theme.css

slick-theme.css

1180 ms

navigation.js

navigation.js

1228 ms

picture_polyfill_loader.js

picture_polyfill_loader.js

1228 ms

snippet.js

snippet.js

50 ms

33 ms

point.css

point.css

25 ms

point.css

point.css

1251 ms

point.js

point.js

28 ms

point_config.js

point_config.js

1228 ms

point_button.js

point_button.js

1322 ms

shop.js

shop.js

1592 ms

container_ucj1EucG.js

container_ucj1EucG.js

39 ms

matomo.js

matomo.js

405 ms

widgit-logo.png

widgit-logo.png

451 ms

search_box.png

search_box.png

452 ms

symbols.png

symbols.png

407 ms

users.png

users.png

449 ms

applications.png

applications.png

529 ms

ip3_logo.png

ip3_logo.png

781 ms

wo_logo.png

wo_logo.png

804 ms

customer.png

customer.png

821 ms

world.png

world.png

820 ms

symbol-friendly3.png

symbol-friendly3.png

928 ms

symbol-friendly2.png

symbol-friendly2.png

1130 ms

design.png

design.png

1193 ms

signage.png

signage.png

1192 ms

design2.png

design2.png

1313 ms

licence.png

licence.png

1204 ms

copyright.png

copyright.png

1327 ms

australia.gif

australia.gif

1535 ms

canada.gif

canada.gif

1605 ms

cyprus.gif

cyprus.gif

1593 ms

czech.gif

czech.gif

1609 ms

danmark.gif

danmark.gif

1672 ms

finland.gif

finland.gif

1732 ms

france.gif

france.gif

1939 ms

greece.gif

greece.gif

1998 ms

italy.gif

italy.gif

1997 ms

latvia.gif

latvia.gif

2013 ms

netherlands.gif

netherlands.gif

2059 ms

norway.gif

norway.gif

2100 ms

poland.gif

poland.gif

2328 ms

portugal.gif

portugal.gif

2358 ms

romania.gif

romania.gif

2381 ms

spain.gif

spain.gif

2391 ms

fsme.woff

fsme.woff

2479 ms

fbevents.js

fbevents.js

17 ms

13 ms

fsme_bold.woff

fsme_bold.woff

2554 ms

respimage.min.js

respimage.min.js

2583 ms

matomo.php

matomo.php

362 ms

fsme_italic.woff

fsme_italic.woff

2573 ms

fsme_bolditalic.woff

fsme_bolditalic.woff

2526 ms

index.php

index.php

2357 ms

index.php

index.php

2467 ms

sweden.gif

sweden.gif

2550 ms

usa.gif

usa.gif

2591 ms

contact2.png

contact2.png

2404 ms

training2.png

training2.png

2495 ms

filetypes.png

filetypes.png

2489 ms

order2.png

order2.png

2548 ms

facebook.png

facebook.png

2484 ms

instagram-small.png

instagram-small.png

2360 ms

twitbird.png

twitbird.png

2366 ms

success_stories.jpg

success_stories.jpg

2578 ms

bar1.png

bar1.png

2514 ms

homepage-image-version-3b.jpg

homepage-image-version-3b.jpg

2847 ms

symbol-sentence-2023.gif

symbol-sentence-2023.gif

2745 ms

reload.png

reload.png

2352 ms

education.jpg

education.jpg

2414 ms

boy.jpg

boy.jpg

2622 ms

health.jpg

health.jpg

2663 ms

breadline.jpg

breadline.jpg

2582 ms

cypcs.jpg

cypcs.jpg

2663 ms

theatre.jpg

theatre.jpg

2640 ms

tourism.jpg

tourism.jpg

2569 ms

uganda.jpg

uganda.jpg

2631 ms

widgit-online.jpg

widgit-online.jpg

2755 ms

InPrint3.jpg

InPrint3.jpg

2621 ms

ip4-is-coming-in-2024-banner-02.png

ip4-is-coming-in-2024-banner-02.png

2784 ms

contact-icon.png

contact-icon.png

2634 ms

mailinglist.png

mailinglist.png

2561 ms

widgit-online-footer.png

widgit-online-footer.png

2601 ms

Widgit-Health-logo-footer.png

Widgit-Health-logo-footer.png

2660 ms

besa_logos_master_rgb.png

besa_logos_master_rgb.png

2654 ms

LW-Employer-logo-e-footer.png

LW-Employer-logo-e-footer.png

2764 ms

point-grey.png

point-grey.png

2627 ms

point_waiticon.gif

point_waiticon.gif

2549 ms

off.gif

off.gif

2473 ms

on.gif

on.gif

2522 ms

point.png

point.png

2301 ms

ajax-loader.gif

ajax-loader.gif

111 ms

back.png

back.png

406 ms

next.png

next.png

391 ms

Accessibility Review

widg.it accessibility score

96

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.

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

widg.it 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

widg.it SEO score

99

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

High

Tap targets are not sized appropriately

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 Widg.it 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 Widg.it 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

widg.it

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