Tools & Wizards About Us
whatsmall.com screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

whatsmall.com

Online Shop for Clothes, Home Accessories, Jewelry, Books, Toys & More | WhatsMall

Page Load Speed

6.4 sec in total

First Response

454 ms

Resources Loaded

5.6 sec

Page Rendered

284 ms

whatsmall.com screenshot

About Website

Visit whatsmall.com now to see the best up-to-date Whats Mall content for Hong Kong and also check out these interesting facts you probably never knew about whatsmall.com

Hong Kong's Premiere Online Shop with the best selection of books, jewelry, baby clothes, gift sets, cellphone accessories, toys & a lot more.

Visit whatsmall.com

Key Findings

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

Performance Metrics

whatsmall.com performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value13.4 s

0/100

25%

SI (Speed Index)

Value6.8 s

35/100

10%

TBT (Total Blocking Time)

Value310 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.714

7/100

15%

TTI (Time to Interactive)

Value7.0 s

53/100

10%

Network Requests Diagram

whatsmall.com

454 ms

whatsmall.com

1424 ms

styles2.css

227 ms

dlmenu.css

450 ms

modernizr.custom.js

655 ms

Our browser made a total of 49 requests to load all elements on the main page. We found that 90% of them (44 requests) were addressed to the original Whatsmall.com, 4% (2 requests) were made to Google-analytics.com and 4% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Whatsmall.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 154.9 kB (32%)

Content Size

480.4 kB

After Optimization

325.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whatsmall.com main page is 480.4 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Javascripts take 195.1 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 28.1 kB

  • Original 35.0 kB
  • After minification 26.5 kB
  • After compression 6.9 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. This page needs HTML code to be minified as it can gain 8.6 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 28.1 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 1.4 kB

  • Original 80.2 kB
  • After minification 78.8 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. Whats Mall images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.4 kB

  • Original 195.1 kB
  • After minification 195.1 kB
  • After compression 193.7 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. This website has mostly compressed JavaScripts.

CSS Optimization

-73%

Potential reduce by 124.1 kB

  • Original 170.1 kB
  • After minification 169.4 kB
  • After compression 46.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. Whatsmall.com needs all CSS files to be minified and compressed as it can save up to 124.1 kB or 73% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (41%)

Requests Now

22

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whatsmall.com

whatsmall.com

454 ms

whatsmall.com

whatsmall.com

1424 ms

styles2.css

styles2.css

227 ms

dlmenu.css

dlmenu.css

450 ms

modernizr.custom.js

modernizr.custom.js

655 ms

rating.css

rating.css

801 ms

jquery-ui.min.css

jquery-ui.min.css

779 ms

jquery-3.7.1.min.js

jquery-3.7.1.min.js

781 ms

function.js

function.js

1373 ms

jquery.elevatezoom2.js

jquery.elevatezoom2.js

801 ms

easyResponsiveTabs.js

easyResponsiveTabs.js

935 ms

common.js

common.js

874 ms

application.js

application.js

897 ms

validations.js

validations.js

1114 ms

jquery.validate.min.js

jquery.validate.min.js

1117 ms

analytics.js

analytics.js

105 ms

whatsmall.png

whatsmall.png

972 ms

we_accept.png

we_accept.png

383 ms

bt_fb.jpg

bt_fb.jpg

564 ms

bt_wb.jpg

bt_wb.jpg

781 ms

verification-h34px.jpg

verification-h34px.jpg

602 ms

Captcha.jpg

Captcha.jpg

758 ms

getImageFileServlet.do

getImageFileServlet.do

2980 ms

getImageFileServlet.do

getImageFileServlet.do

2155 ms

getImageFileServlet.do

getImageFileServlet.do

1976 ms

getImageFileServlet.do

getImageFileServlet.do

1996 ms

getImageFileServlet.do

getImageFileServlet.do

2488 ms

getImageFileServlet.do

getImageFileServlet.do

2270 ms

getImageFileServlet.do

getImageFileServlet.do

2212 ms

getImageFileServlet.do

getImageFileServlet.do

2465 ms

getImageFileServlet.do

getImageFileServlet.do

2613 ms

getImageFileServlet.do

getImageFileServlet.do

2447 ms

getImageFileServlet.do

getImageFileServlet.do

2488 ms

getImageFileServlet.do

getImageFileServlet.do

2683 ms

getImageFileServlet.do

getImageFileServlet.do

2702 ms

getImageFileServlet.do

getImageFileServlet.do

2726 ms

getImageFileServlet.do

getImageFileServlet.do

2708 ms

getImageFileServlet.do

getImageFileServlet.do

2842 ms

getImageFileServlet.do

getImageFileServlet.do

2916 ms

getImageFileServlet.do

getImageFileServlet.do

2938 ms

getImageFileServlet.do

getImageFileServlet.do

2927 ms

getImageFileServlet.do

getImageFileServlet.do

2964 ms

header_icon_1x.png

header_icon_1x.png

754 ms

ga.js

ga.js

53 ms

icomoon.woff

icomoon.woff

739 ms

icomoon.eot

icomoon.eot

729 ms

collect

collect

30 ms

__utm.gif

__utm.gif

15 ms

js

js

64 ms

Accessibility Review

whatsmall.com accessibility score

75

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 IDs are not unique

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

Best Practices

whatsmall.com best practices score

58

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

whatsmall.com SEO score

83

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

    EN

  • Encoding

    UTF-8

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

whatsmall.com

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