Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 81

    SEO

    Google-friendlier than
    43% of websites

squarelet.com

Squarelet ® | eCommerce Shopping Cart Malaysia | For Founder with Agent and Dropship

Page Load Speed

27.7 sec in total

First Response

558 ms

Resources Loaded

24.5 sec

Page Rendered

2.7 sec

squarelet.com screenshot

About Website

Welcome to squarelet.com homepage info - get ready to check Squarelet best content for Malaysia right away, or after learning these important things about squarelet.com

Powerful and user-friendly eCommerce Shopping Cart Malaysia that is designed for Dropship, Wholesale and Retail. Squarelet takes care of everything while you focus on growing your online business.

Visit squarelet.com

Key Findings

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

Performance Metrics

squarelet.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value40.8 s

0/100

10%

TBT (Total Blocking Time)

Value77,200 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value119.9 s

0/100

10%

Network Requests Diagram

squarelet.com

558 ms

Base.aspx

701 ms

Base.aspx

238 ms

Satellite.aspx

236 ms

Satellite.aspx

251 ms

Our browser made a total of 464 requests to load all elements on the main page. We found that 12% of them (55 requests) were addressed to the original Squarelet.com, 86% (399 requests) were made to Img.squarelet.com and 1% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5.3 sec) relates to the external source Img.squarelet.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.6 MB (41%)

Content Size

8.7 MB

After Optimization

5.1 MB

In fact, the total size of Squarelet.com main page is 8.7 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.3 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 2.5 MB

  • Original 3.1 MB
  • After minification 3.1 MB
  • After compression 571.5 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 2.5 MB or 82% of the original size.

Image Optimization

-16%

Potential reduce by 840.6 kB

  • Original 5.3 MB
  • After minification 4.4 MB

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. Obviously, Squarelet needs image optimization as it can save up to 840.6 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-37%

Potential reduce by 41.8 kB

  • Original 114.4 kB
  • After minification 87.8 kB
  • After compression 72.6 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 41.8 kB or 37% of the original size.

CSS Optimization

-88%

Potential reduce by 188.1 kB

  • Original 213.4 kB
  • After minification 143.5 kB
  • After compression 25.3 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. Squarelet.com needs all CSS files to be minified and compressed as it can save up to 188.1 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (5%)

Requests Now

452

After Optimization

430

The browser has sent 452 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Squarelet. 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.

Accessibility Review

squarelet.com accessibility score

56

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

[aria-*] attributes do not match their roles

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

Image elements do not have [alt] attributes

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

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

Best Practices

squarelet.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

squarelet.com SEO score

81

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

High

Tap targets are not sized appropriately

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

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