Tools & Wizards About Us
whatspie.com screenshot

Report Summary

  • 32

    Performance

    Renders faster than
    52% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

whatspie.com

Whatspie - Enterprise ready Whatsapp API and BOT service

Page Load Speed

5.8 sec in total

First Response

335 ms

Resources Loaded

4.7 sec

Page Rendered

782 ms

whatspie.com screenshot

About Website

Welcome to whatspie.com homepage info - get ready to check Whatspie best content for Indonesia right away, or after learning these important things about whatspie.com

Whatspie is an Enterprise ready unofficial WhatsApp API and BOT Service, allow you to sending notification to customer using WhatsApp API from your App

Visit whatspie.com

Key Findings

We analyzed Whatspie.com page load time and found that the first response time was 335 ms and then it took 5.4 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

whatspie.com performance score

32

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value8.3 s

2/100

25%

SI (Speed Index)

Value10.8 s

6/100

10%

TBT (Total Blocking Time)

Value690 ms

43/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

whatspie.com

335 ms

autoptimize_070d039ad613f0e82a7503a7360686b8.css

26 ms

autoptimize_single_1a08eb33e892c55c0a0d4293f96251b1.css

268 ms

autoptimize_single_26b1913565c98d7573eb650f9942e1e9.css

274 ms

autoptimize_single_ad2d74cc1582026558953e7339ccedb7.css

270 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 48% of them (22 requests) were addressed to the original Whatspie.com, 48% (22 requests) were made to Fonts.gstatic.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (919 ms) belongs to the original domain Whatspie.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 150.6 kB (43%)

Content Size

353.7 kB

After Optimization

203.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whatspie.com main page is 353.7 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. 60% of websites need less resources to load. Javascripts take 120.7 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 69.0 kB

  • Original 82.2 kB
  • After minification 82.2 kB
  • After compression 13.3 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 69.0 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 60.2 kB
  • After minification 60.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. Whatspie images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 105 B

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

CSS Optimization

-90%

Potential reduce by 81.5 kB

  • Original 90.6 kB
  • After minification 9.2 kB
  • After compression 9.1 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. Whatspie.com needs all CSS files to be minified and compressed as it can save up to 81.5 kB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (63%)

Requests Now

19

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whatspie.com

whatspie.com

335 ms

autoptimize_070d039ad613f0e82a7503a7360686b8.css

autoptimize_070d039ad613f0e82a7503a7360686b8.css

26 ms

autoptimize_single_1a08eb33e892c55c0a0d4293f96251b1.css

autoptimize_single_1a08eb33e892c55c0a0d4293f96251b1.css

268 ms

autoptimize_single_26b1913565c98d7573eb650f9942e1e9.css

autoptimize_single_26b1913565c98d7573eb650f9942e1e9.css

274 ms

autoptimize_single_ad2d74cc1582026558953e7339ccedb7.css

autoptimize_single_ad2d74cc1582026558953e7339ccedb7.css

270 ms

autoptimize_single_2cdd2494a2bfa2e8755afc6094e42fa1.css

autoptimize_single_2cdd2494a2bfa2e8755afc6094e42fa1.css

271 ms

autoptimize_single_3d821fb1f2751ad490413d4c21fdf2c3.css

autoptimize_single_3d821fb1f2751ad490413d4c21fdf2c3.css

318 ms

css

css

104 ms

js

js

107 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

100 ms

wp-polyfill.min.js

wp-polyfill.min.js

102 ms

hooks.min.js

hooks.min.js

102 ms

i18n.min.js

i18n.min.js

102 ms

autoptimize_16216cfa4161dafbb3712f63d7876b97.js

autoptimize_16216cfa4161dafbb3712f63d7876b97.js

103 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

36 ms

BG-HomePage-High.png

BG-HomePage-High.png

89 ms

Shapes-icons.png

Shapes-icons.png

282 ms

BG-TEAN-Home.png

BG-TEAN-Home.png

919 ms

BG-Testemonials-home-page.png

BG-Testemonials-home-page.png

281 ms

CTA-Shapes.png

CTA-Shapes.png

261 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

20 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

28 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

46 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

61 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

61 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

63 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

62 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

64 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

58 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

64 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

65 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

66 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

68 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

67 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

67 ms

w8gdH283Tvk__Lua32TysjIfp8uK.ttf

w8gdH283Tvk__Lua32TysjIfp8uK.ttf

102 ms

fa-solid-900.woff

fa-solid-900.woff

358 ms

fa-regular-400.woff

fa-regular-400.woff

287 ms

KFOkCnqEu92Fr1Mu51xIIzc.ttf

KFOkCnqEu92Fr1Mu51xIIzc.ttf

102 ms

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

KFOjCnqEu92Fr1Mu51S7ACc6CsE.ttf

103 ms

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

KFOjCnqEu92Fr1Mu51TjASc6CsE.ttf

104 ms

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

KFOiCnqEu92Fr1Mu51QrEzAdKg.ttf

104 ms

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

KFOjCnqEu92Fr1Mu51TzBic6CsE.ttf

104 ms

KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf

KFOjCnqEu92Fr1Mu51TLBCc6CsE.ttf

105 ms

eicons.woff

eicons.woff

667 ms

fa-brands-400.woff

fa-brands-400.woff

470 ms

Accessibility Review

whatspie.com accessibility score

93

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

whatspie.com 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

whatspie.com SEO score

97

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

whatspie.com

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