Tools & Wizards About Us
websmith.digital screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

websmith.digital

WebSmith.Digital Website and Landing Page Builder

Page Load Speed

1.7 sec in total

First Response

147 ms

Resources Loaded

1.4 sec

Page Rendered

177 ms

websmith.digital screenshot

About Website

Welcome to websmith.digital homepage info - get ready to check Web Smith best content for Malaysia right away, or after learning these important things about websmith.digital

A +400 professionally designed blocks allowing you to start building sites and pages instantly with Easy to use drag & drop builder!

Visit websmith.digital

Key Findings

We analyzed Websmith.digital page load time and found that the first response time was 147 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

websmith.digital performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.8 s

12/100

10%

LCP (Largest Contentful Paint)

Value8.7 s

1/100

25%

SI (Speed Index)

Value8.7 s

16/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.081

94/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

websmith.digital

147 ms

websmith.digital

491 ms

bootstrap.css

89 ms

stack-interface.css

113 ms

socicon.css

110 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 68% of them (32 requests) were addressed to the original Websmith.digital, 23% (11 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (491 ms) belongs to the original domain Websmith.digital.

Page Optimization Overview & Recommendations

Page size can be reduced by 698.8 kB (74%)

Content Size

946.2 kB

After Optimization

247.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Websmith.digital main page is 946.2 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. 40% of websites need less resources to load. Javascripts take 437.5 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 25.0 kB

  • Original 28.1 kB
  • After minification 16.3 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 11.8 kB, which is 42% 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 25.0 kB or 89% of the original size.

Image Optimization

-3%

Potential reduce by 2.3 kB

  • Original 73.7 kB
  • After minification 71.4 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. Web Smith images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 323.6 kB

  • Original 437.5 kB
  • After minification 386.9 kB
  • After compression 113.9 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 323.6 kB or 74% of the original size.

CSS Optimization

-86%

Potential reduce by 347.9 kB

  • Original 406.8 kB
  • After minification 333.8 kB
  • After compression 58.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. Websmith.digital needs all CSS files to be minified and compressed as it can save up to 347.9 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (84%)

Requests Now

32

After Optimization

5

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

websmith.digital

websmith.digital

147 ms

websmith.digital

websmith.digital

491 ms

bootstrap.css

bootstrap.css

89 ms

stack-interface.css

stack-interface.css

113 ms

socicon.css

socicon.css

110 ms

lightbox.min.css

lightbox.min.css

110 ms

flickity.css

flickity.css

112 ms

iconsmind.css

iconsmind.css

170 ms

jquery.steps.css

jquery.steps.css

121 ms

theme.css

theme.css

228 ms

custom.css

custom.css

134 ms

font-rubiklato.css

font-rubiklato.css

137 ms

css

css

38 ms

css

css

56 ms

icon

icon

59 ms

sbjclf34tk2ks5me6u7qzhlienc9zcij

sbjclf34tk2ks5me6u7qzhlienc9zcij

39 ms

jquery-3.1.1.min.js

jquery-3.1.1.min.js

183 ms

flickity.min.js

flickity.min.js

158 ms

easypiechart.min.js

easypiechart.min.js

156 ms

parallax.js

parallax.js

162 ms

typed.min.js

typed.min.js

195 ms

datepicker.js

datepicker.js

201 ms

isotope.min.js

isotope.min.js

321 ms

ytplayer.min.js

ytplayer.min.js

214 ms

lightbox.min.js

lightbox.min.js

219 ms

granim.min.js

granim.min.js

223 ms

jquery.steps.min.js

jquery.steps.min.js

320 ms

countdown.min.js

countdown.min.js

320 ms

twitterfetcher.min.js

twitterfetcher.min.js

321 ms

spectragram.min.js

spectragram.min.js

321 ms

smooth-scroll.min.js

smooth-scroll.min.js

321 ms

scripts.js

scripts.js

323 ms

logo.png

logo.png

321 ms

file_1614870185.JPG

file_1614870185.JPG

321 ms

S6u9w4BMUTPHh6UVSwiPHw.woff

S6u9w4BMUTPHh6UVSwiPHw.woff

51 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

52 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0Uz.woff

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0Uz.woff

64 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0Uz.woff

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0Uz.woff

79 ms

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFV0Uz.woff

iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFV0Uz.woff

78 ms

iconsmind.woff

iconsmind.woff

390 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

79 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVQ.woff

78 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVQ.woff

78 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

78 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVQ.woff

79 ms

S6u8w4BMUTPHjxsAXC-s.woff

S6u8w4BMUTPHjxsAXC-s.woff

80 ms

stack-interface.woff

stack-interface.woff

66 ms

Accessibility Review

websmith.digital accessibility score

88

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.

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

Links do not have a discernible name

Best Practices

websmith.digital 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

websmith.digital SEO score

89

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

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 Websmith.digital 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 Websmith.digital 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

websmith.digital

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