Tools & Wizards About Us
squizz.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

squizz.com

SQUIZZ.com - Do What Counts

Page Load Speed

6.2 sec in total

First Response

447 ms

Resources Loaded

5.7 sec

Page Rendered

54 ms

squizz.com screenshot

About Website

Visit squizz.com now to see the best up-to-date SQUIZZ content and also check out these interesting facts you probably never knew about squizz.com

Home Page of SQUIZZ.com, The world's first Social Ecommerce Platform. Signup for free, login, and learn about the SQUIZZ.com platform.

Visit squizz.com

Key Findings

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

Performance Metrics

squizz.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

28/100

10%

LCP (Largest Contentful Paint)

Value10.4 s

0/100

25%

SI (Speed Index)

Value14.0 s

1/100

10%

TBT (Total Blocking Time)

Value1,750 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.204

61/100

15%

TTI (Time to Interactive)

Value16.0 s

6/100

10%

Network Requests Diagram

squizz.com

447 ms

www.squizz.com

430 ms

www.squizz.com

906 ms

yui-min.js

447 ms

core_3_02.js

658 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 95.6 kB (7%)

Content Size

1.3 MB

After Optimization

1.2 MB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Squizz.com main page is 1.3 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. 35% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 18.7 kB

  • Original 22.7 kB
  • After minification 22.2 kB
  • After compression 4.0 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 18.7 kB or 83% of the original size.

JavaScript Optimization

-6%

Potential reduce by 75.6 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 1.2 MB

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.

CSS Optimization

-9%

Potential reduce by 1.3 kB

  • Original 13.9 kB
  • After minification 13.7 kB
  • After compression 12.6 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. Squizz.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 80 (98%)

Requests Now

82

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

squizz.com

squizz.com

447 ms

www.squizz.com

www.squizz.com

430 ms

www.squizz.com

www.squizz.com

906 ms

yui-min.js

yui-min.js

447 ms

core_3_02.js

core_3_02.js

658 ms

lang-en-au_4_07.js

lang-en-au_4_07.js

1112 ms

open-sans.css

open-sans.css

697 ms

ui_basic_large_4_04.css

ui_basic_large_4_04.css

705 ms

ui_home_2_38.css

ui_home_2_38.css

706 ms

ui_user_bar_2_38.css

ui_user_bar_2_38.css

707 ms

home_4_04.js

home_4_04.js

868 ms

core-mvc_1_70.js

core-mvc_1_70.js

909 ms

user_4_04.js

user_4_04.js

917 ms

user-session_3_15.js

user-session_3_15.js

919 ms

user-bar_4_04.js

user-bar_4_04.js

919 ms

user-bar-order-purchase_2_04.js

user-bar-order-purchase_2_04.js

1077 ms

org_3_01.js

org_3_01.js

1121 ms

org-order-purchase_1_59_4.js

org-order-purchase_1_59_4.js

1143 ms

org-payment_2_34.js

org-payment_2_34.js

1145 ms

org-account-customer_3_02.js

org-account-customer_3_02.js

1276 ms

org-account-customer-record_1_72.js

org-account-customer-record_1_72.js

1288 ms

org-account-supplier_3_10.js

org-account-supplier_3_10.js

1323 ms

org-account-supplier-record_1_70.js

org-account-supplier-record_1_70.js

1334 ms

org-product_2_26.js

org-product_2_26.js

1357 ms

org-order-purchase-import_1_09.js

org-order-purchase-import_1_09.js

1358 ms

org-order-purchase-procurement_1_52.js

org-order-purchase-procurement_1_52.js

1490 ms

org-invoice-supplier_1_59_4.js

org-invoice-supplier_1_59_4.js

1522 ms

org-invoice-supplier-import_3_11.js

org-invoice-supplier-import_3_11.js

1537 ms

search-org-category_1_68.js

search-org-category_1_68.js

1546 ms

squizz_react_4_07_1.js

squizz_react_4_07_1.js

2671 ms

widget-base.css

widget-base.css

1007 ms

cssbutton-min.css

cssbutton-min.css

1037 ms

widget-modality.css

widget-modality.css

1069 ms

widget-stack.css

widget-stack.css

1087 ms

panel.css

panel.css

1097 ms

oop-min.js

oop-min.js

329 ms

attribute-core-min.js

attribute-core-min.js

224 ms

event-custom-base-min.js

event-custom-base-min.js

327 ms

event-custom-complex-min.js

event-custom-complex-min.js

340 ms

attribute-observable-min.js

attribute-observable-min.js

339 ms

attribute-extras-min.js

attribute-extras-min.js

448 ms

attribute-base-min.js

attribute-base-min.js

548 ms

attribute-complex-min.js

attribute-complex-min.js

550 ms

base-core-min.js

base-core-min.js

559 ms

base-observable-min.js

base-observable-min.js

570 ms

base-base-min.js

base-base-min.js

663 ms

pluginhost-base-min.js

pluginhost-base-min.js

761 ms

pluginhost-config-min.js

pluginhost-config-min.js

767 ms

base-pluginhost-min.js

base-pluginhost-min.js

778 ms

classnamemanager-min.js

classnamemanager-min.js

785 ms

event-base-min.js

event-base-min.js

892 ms

dom-core-min.js

dom-core-min.js

976 ms

dom-base-min.js

dom-base-min.js

980 ms

selector-native-min.js

selector-native-min.js

988 ms

selector-min.js

selector-min.js

998 ms

node-core-min.js

node-core-min.js

1107 ms

dom-style-min.js

dom-style-min.js

1096 ms

node-base-min.js

node-base-min.js

1191 ms

event-synthetic-min.js

event-synthetic-min.js

1194 ms

event-focus-min.js

event-focus-min.js

1197 ms

node-style-min.js

node-style-min.js

1213 ms

widget-base-min.js

widget-base-min.js

1314 ms

widget-htmlparser-min.js

widget-htmlparser-min.js

1321 ms

widget-skin-min.js

widget-skin-min.js

1406 ms

event-delegate-min.js

event-delegate-min.js

1409 ms

node-event-delegate-min.js

node-event-delegate-min.js

1407 ms

widget-uievents-min.js

widget-uievents-min.js

1427 ms

base-build-min.js

base-build-min.js

1527 ms

event-key-min.js

event-key-min.js

1534 ms

event-outside-min.js

event-outside-min.js

1624 ms

widget-autohide-min.js

widget-autohide-min.js

1403 ms

escape-min.js

escape-min.js

1304 ms

button-core-min.js

button-core-min.js

1317 ms

node-pluginhost-min.js

node-pluginhost-min.js

1408 ms

button-plugin-min.js

button-plugin-min.js

1411 ms

widget-stdmod-min.js

widget-stdmod-min.js

1395 ms

widget-buttons-min.js

widget-buttons-min.js

1300 ms

widget-modality-min.js

widget-modality-min.js

1300 ms

dom-screen-min.js

dom-screen-min.js

1300 ms

node-screen-min.js

node-screen-min.js

1409 ms

widget-position-min.js

widget-position-min.js

1319 ms

widget-position-align-min.js

widget-position-align-min.js

1292 ms

widget-position-constrain-min.js

widget-position-constrain-min.js

1295 ms

widget-stack-min.js

widget-stack-min.js

1286 ms

panel-min.js

panel-min.js

1287 ms

Accessibility Review

squizz.com accessibility score

80

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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>).

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

squizz.com best practices score

83

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

Missing source maps for large first-party JavaScript

SEO Factors

squizz.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

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

    N/A

  • Encoding

    UTF-8

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

squizz.com

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