Tools & Wizards About Us
whoscammed.me screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

whoscammed.me

WSM | Home

Page Load Speed

948 ms in total

First Response

26 ms

Resources Loaded

560 ms

Page Rendered

362 ms

whoscammed.me screenshot

About Website

Visit whoscammed.me now to see the best up-to-date Whoscammed content for Canada and also check out these interesting facts you probably never knew about whoscammed.me

Look up what you think might be a scam and confirm for yourself

Visit whoscammed.me

Key Findings

We analyzed Whoscammed.me page load time and found that the first response time was 26 ms and then it took 922 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

whoscammed.me performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.6 s

63/100

10%

LCP (Largest Contentful Paint)

Value21.4 s

0/100

25%

SI (Speed Index)

Value4.3 s

76/100

10%

TBT (Total Blocking Time)

Value1,060 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.054

98/100

15%

TTI (Time to Interactive)

Value10.5 s

23/100

10%

Network Requests Diagram

whoscammed.me

26 ms

css2

35 ms

css2

52 ms

bootstrap.min.css

63 ms

font-awesome.min.css

49 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 70% of them (23 requests) were addressed to the original Whoscammed.me, 24% (8 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (451 ms) belongs to the original domain Whoscammed.me.

Page Optimization Overview & Recommendations

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

Content Size

308.4 kB

After Optimization

285.9 kB

  • HTML
  • Images

In fact, the total size of Whoscammed.me main page is 308.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. 40% of websites need less resources to load. Images take 289.7 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 16.1 kB

  • Original 18.7 kB
  • After minification 9.1 kB
  • After compression 2.6 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 9.6 kB, which is 51% 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 16.1 kB or 86% of the original size.

Image Optimization

-2%

Potential reduce by 6.4 kB

  • Original 289.7 kB
  • After minification 283.3 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. Whoscammed images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 13 (57%)

Requests Now

23

After Optimization

10

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whoscammed.me

whoscammed.me

26 ms

css2

css2

35 ms

css2

css2

52 ms

bootstrap.min.css

bootstrap.min.css

63 ms

font-awesome.min.css

font-awesome.min.css

49 ms

elegant-icons.css

elegant-icons.css

148 ms

owl.carousel.min.css

owl.carousel.min.css

93 ms

slicknav.min.css

slicknav.min.css

128 ms

slick.css

slick.css

87 ms

style.css

style.css

174 ms

logo.png

logo.png

204 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

128 ms

bootstrap.min.js

bootstrap.min.js

334 ms

jquery.slicknav.js

jquery.slicknav.js

205 ms

owl.carousel.min.js

owl.carousel.min.js

210 ms

slick.min.js

slick.min.js

332 ms

main.js

main.js

349 ms

link.png

link.png

347 ms

services-1.png

services-1.png

378 ms

services-2.png

services-2.png

347 ms

services-3.png

services-3.png

359 ms

services-4.png

services-4.png

369 ms

ripple-1s.gif

ripple-1s.gif

451 ms

testimonial-bg.jpg

testimonial-bg.jpg

298 ms

pxiEyp8kv8JHgFVrFJA.ttf

pxiEyp8kv8JHgFVrFJA.ttf

24 ms

pxiByp8kv8JHgFVrLGT9V1s.ttf

pxiByp8kv8JHgFVrLGT9V1s.ttf

29 ms

pxiByp8kv8JHgFVrLDz8V1s.ttf

pxiByp8kv8JHgFVrLDz8V1s.ttf

47 ms

pxiByp8kv8JHgFVrLEj6V1s.ttf

pxiByp8kv8JHgFVrLEj6V1s.ttf

42 ms

pxiByp8kv8JHgFVrLCz7V1s.ttf

pxiByp8kv8JHgFVrLCz7V1s.ttf

130 ms

pxiByp8kv8JHgFVrLDD4V1s.ttf

pxiByp8kv8JHgFVrLDD4V1s.ttf

47 ms

pxiByp8kv8JHgFVrLBT5V1s.ttf

pxiByp8kv8JHgFVrLBT5V1s.ttf

130 ms

MCoTzAn-1s3IGyJMZaA.ttf

MCoTzAn-1s3IGyJMZaA.ttf

34 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

140 ms

Accessibility Review

whoscammed.me accessibility score

82

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-hidden="true"] elements contain focusable descendents

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

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

whoscammed.me 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

whoscammed.me SEO score

90

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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

    ZX

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whoscammed.me can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed language. Our system also found out that Whoscammed.me 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

whoscammed.me

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