Tools & Wizards About Us
phantom.us screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

phantom.us

Splunk SOAR | Splunk

Page Load Speed

838 ms in total

First Response

11 ms

Resources Loaded

356 ms

Page Rendered

471 ms

phantom.us screenshot

About Website

Visit phantom.us now to see the best up-to-date Phantom content for Bangladesh and also check out these interesting facts you probably never knew about phantom.us

Splunk SOAR lets you automate repetitive tasks, investigate and respond to security incidents in seconds, and increase productivity to better protect your business.

Visit phantom.us

Key Findings

We analyzed Phantom.us page load time and found that the first response time was 11 ms and then it took 827 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

phantom.us performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

55/100

25%

SI (Speed Index)

Value4.9 s

65/100

10%

TBT (Total Blocking Time)

Value430 ms

65/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value9.3 s

31/100

10%

Network Requests Diagram

phantom.us

11 ms

www.phantom.us

42 ms

css

67 ms

styles_20160314032528.css

6 ms

SourceSansPro.css

28 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 74% of them (28 requests) were addressed to the original Phantom.us, 18% (7 requests) were made to Fonts.gstatic.com and 5% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (112 ms) relates to the external source Fonts.gstatic.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 368.9 kB (54%)

Content Size

688.1 kB

After Optimization

319.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Phantom.us main page is 688.1 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 296.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 35.5 kB

  • Original 45.5 kB
  • After minification 37.1 kB
  • After compression 10.0 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.4 kB, which is 18% 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 35.5 kB or 78% of the original size.

Image Optimization

-11%

Potential reduce by 23.0 kB

  • Original 205.3 kB
  • After minification 182.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. Obviously, Phantom needs image optimization as it can save up to 23.0 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 195.9 kB

  • Original 296.6 kB
  • After minification 281.9 kB
  • After compression 100.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 195.9 kB or 66% of the original size.

CSS Optimization

-81%

Potential reduce by 114.5 kB

  • Original 140.8 kB
  • After minification 140.6 kB
  • After compression 26.3 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. Phantom.us needs all CSS files to be minified and compressed as it can save up to 114.5 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

23

After Optimization

20

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

phantom.us

phantom.us

11 ms

www.phantom.us

www.phantom.us

42 ms

css

css

67 ms

styles_20160314032528.css

styles_20160314032528.css

6 ms

SourceSansPro.css

SourceSansPro.css

28 ms

font-awesome.min.css

font-awesome.min.css

28 ms

main.js

main.js

31 ms

form.js

form.js

29 ms

logo.svg

logo.svg

83 ms

analytics.js

analytics.js

102 ms

rsa_isb_logo.png

rsa_isb_logo.png

33 ms

touch-bg.jpg

touch-bg.jpg

31 ms

scroll-prompt.png

scroll-prompt.png

25 ms

light-bulb-icon.png

light-bulb-icon.png

31 ms

rocket-ship-icon.png

rocket-ship-icon.png

24 ms

molecule-icon.png

molecule-icon.png

51 ms

oliver-friedrichs.jpg

oliver-friedrichs.jpg

51 ms

sourabh-satish.jpg

sourabh-satish.jpg

52 ms

erich-baumgartner.jpg

erich-baumgartner.jpg

54 ms

cp-morey.jpg

cp-morey.jpg

51 ms

dan-ramaswami.jpg

dan-ramaswami.jpg

52 ms

businesswire.png

businesswire.png

62 ms

wsj.png

wsj.png

54 ms

tc.png

tc.png

54 ms

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf

54 ms

ODelI1aHBYDBqgeIAH2zlEY6Fu39Tt9XkmtSosaMoEA.ttf

ODelI1aHBYDBqgeIAH2zlEY6Fu39Tt9XkmtSosaMoEA.ttf

62 ms

toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf

toadOcfmlt9b38dHJxOBGMw1o1eFRj7wYC6JbISqOjY.ttf

58 ms

toadOcfmlt9b38dHJxOBGPS42wKzre0cxmO5m5GyTsY.ttf

toadOcfmlt9b38dHJxOBGPS42wKzre0cxmO5m5GyTsY.ttf

76 ms

toadOcfmlt9b38dHJxOBGNF-01od694vbXd2r4ICkqU.ttf

toadOcfmlt9b38dHJxOBGNF-01od694vbXd2r4ICkqU.ttf

87 ms

toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf

toadOcfmlt9b38dHJxOBGNNE-IuDiR70wI4zXaKqWCM.ttf

61 ms

toadOcfmlt9b38dHJxOBGBRq_IsDXucKYMk4-diqPEc.ttf

toadOcfmlt9b38dHJxOBGBRq_IsDXucKYMk4-diqPEc.ttf

100 ms

toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf

toadOcfmlt9b38dHJxOBGLsbIrGiHa6JIepkyt5c0A0.ttf

61 ms

toadOcfmlt9b38dHJxOBGLlcMrNrsnL9dgADnXgYJjs.ttf

toadOcfmlt9b38dHJxOBGLlcMrNrsnL9dgADnXgYJjs.ttf

90 ms

toadOcfmlt9b38dHJxOBGBPPOa1q11iOmmM9mDHHHX4.ttf

toadOcfmlt9b38dHJxOBGBPPOa1q11iOmmM9mDHHHX4.ttf

60 ms

5AUH_bu0Kry_Rnde4VJNk6CWcynf_cDxXwCLxiixG1c.ttf

5AUH_bu0Kry_Rnde4VJNk6CWcynf_cDxXwCLxiixG1c.ttf

99 ms

sIB6Zipah1bAnMw6oQYPEHYhjbSpvc47ee6xR_80Hnw.ttf

sIB6Zipah1bAnMw6oQYPEHYhjbSpvc47ee6xR_80Hnw.ttf

112 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

60 ms

collect

collect

39 ms

Accessibility Review

phantom.us 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-*] attributes do not match their roles

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

[lang] attributes do not have a valid value

Best Practices

phantom.us best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

phantom.us SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phantom.us can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Phantom.us 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

phantom.us

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