Tools & Wizards About Us
virussign.com screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    64% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

virussign.com

VirusSign - Open Malware Database & Repository

Page Load Speed

5 sec in total

First Response

219 ms

Resources Loaded

4.3 sec

Page Rendered

454 ms

virussign.com screenshot

About Website

Visit virussign.com now to see the best up-to-date Virus Sign content for Vietnam and also check out these interesting facts you probably never knew about virussign.com

Giant malware database dedicated to combating threats in the digital world. The biggest malware samples repository for researchers.

Visit virussign.com

Key Findings

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

Performance Metrics

virussign.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value200 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.4 s

24/100

10%

Network Requests Diagram

virussign.com

219 ms

www.virussign.com

1112 ms

style.min.css

221 ms

style.min.css

293 ms

style.min.css

223 ms

Our browser made a total of 41 requests to load all elements on the main page. We found that 98% of them (40 requests) were addressed to the original Virussign.com, 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.4 sec) belongs to the original domain Virussign.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 523.5 kB (28%)

Content Size

1.9 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Virussign.com main page is 1.9 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. 30% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 82.5 kB

  • Original 99.6 kB
  • After minification 99.1 kB
  • After compression 17.1 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 82.5 kB or 83% of the original size.

Image Optimization

-8%

Potential reduce by 109.1 kB

  • Original 1.3 MB
  • After minification 1.2 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. Virus Sign images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 256.9 kB

  • Original 390.1 kB
  • After minification 389.7 kB
  • After compression 133.2 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 256.9 kB or 66% of the original size.

CSS Optimization

-85%

Potential reduce by 74.9 kB

  • Original 88.6 kB
  • After minification 81.7 kB
  • After compression 13.7 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. Virussign.com needs all CSS files to be minified and compressed as it can save up to 74.9 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (44%)

Requests Now

39

After Optimization

22

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

virussign.com

virussign.com

219 ms

www.virussign.com

www.virussign.com

1112 ms

style.min.css

style.min.css

221 ms

style.min.css

style.min.css

293 ms

style.min.css

style.min.css

223 ms

style.min.css

style.min.css

221 ms

styles.css

styles.css

226 ms

jquery.min.js

jquery.min.js

369 ms

jquery-migrate.min.js

jquery-migrate.min.js

228 ms

wdt.chartsRender.min.js

wdt.chartsRender.min.js

223 ms

Chart.js

Chart.js

518 ms

wdt.chartJS.min.js

wdt.chartJS.min.js

297 ms

view.min.js

view.min.js

296 ms

common.js

common.js

297 ms

js

js

77 ms

infoot.js

infoot.js

295 ms

simpleParallax.min.js

simpleParallax.min.js

317 ms

countup.min.js

countup.min.js

316 ms

typed.min.js

typed.min.js

318 ms

scripts.js

scripts.js

316 ms

wp-polyfill-importmap.min.js

wp-polyfill-importmap.min.js

76 ms

ico-data01.svg

ico-data01.svg

314 ms

ico-malware02.svg

ico-malware02.svg

322 ms

ico-analysis02.svg

ico-analysis02.svg

326 ms

ico-ai01.svg

ico-ai01.svg

331 ms

ico-data03.svg

ico-data03.svg

333 ms

ico-shield.svg

ico-shield.svg

385 ms

client_photo_01-e1686868454388.jpg

client_photo_01-e1686868454388.jpg

540 ms

client_photo_02.jpg

client_photo_02.jpg

1302 ms

client_photo_03.jpg

client_photo_03.jpg

550 ms

logo-google.svg

logo-google.svg

406 ms

logo-microsoft.svg

logo-microsoft.svg

414 ms

logo-nsuflorida.svg

logo-nsuflorida.svg

457 ms

logo-norton.svg

logo-norton.svg

479 ms

ico-trusted01.svg

ico-trusted01.svg

488 ms

ico-customized.svg

ico-customized.svg

530 ms

partner03-1024x819.png

partner03-1024x819.png

2420 ms

logo-virussign.png

logo-virussign.png

90 ms

banner01.png

banner01.png

664 ms

data01.png

data01.png

369 ms

logo-virussign-white.svg

logo-virussign-white.svg

90 ms

Accessibility Review

virussign.com accessibility score

98

Accessibility Issues

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

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

virussign.com SEO score

100

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

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

virussign.com

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