Analyze

stanley.net: RealNames | A more meaningful email address

Get an email address at stanley.net. It's ad-free, reliable email that's based on your own name | stanley.net

Page load speed analysis

  • 77/100

    Good result
  • 7

    Successful tests
  • 1

    Failed test
  • First response

    143 ms

  • Resources loaded

    951 ms

  • Page rendered

    190 ms

  • Total page load time

    1.3 sec

Click here to check amazing Stanley content. Otherwise, check out these important facts you probably never knew about stanley.net

We analyzed Stanley.net page load time and found that the first response time was 143 ms and then it took 1.1 sec 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.

Page optimization

  • HTML 10.8 kB
    Images 508.5 kB
    Javascripts 266.6 kB
    CSS 146.1 kB

    In fact, the total size of Stanley.net main page is 931.9 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. 30% of websites need less resources to load. Images take 508.5 kB which makes up the majority of the site volume.

    • Original 10.8 kB
    • After minification 10.7 kB
    • After compression 4.6 kB

    HTML optimization

    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 6.2 kB or 58% of the original size.

    • Original 508.5 kB
    • After optimization 483.2 kB

    Image optimization

    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. Stanley images are well optimized though.

    • Original 266.6 kB
    • After minification 266.6 kB
    • After compression 91.8 kB

    JavaScript optimization

    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 174.8 kB or 66% of the original size.

    • Original 146.1 kB
    • After minification 145.7 kB
    • After compression 22.6 kB

    CSS optimization

    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. Stanley.net needs all CSS files to be minified and compressed as it can save up to 123.4 kB or 85% of the original size.

Network requests diagram

  • stanley.net
  • application-ea04a682655117ac21a0f78101c752d0.css
  • application-b515ec105640bd3304f23625f6713d1c.js
  • main-a1f93a847a0847298964a9fe0248e070.js
  • gtm.js
  • realnames-50923a6bf6a76a632d7f744137b6842b.png
  • realnames_homepage_woman-42db4bb645f96479b8cfa2d2eda3a05b.png
  • tucows-174830705ee53395b224d33bcc8f5410.png
  • cc-584a2f87fa77911578e9cbc86c8f22d2.png
  • avenir_light-ab4ce772a4827ec3925645afe3dc4c67.ttf
  • avenirnext-ultralight-3433515b53209b9523ab4b29ec5e1569.ttf
  • avenir_bold-c7d850735b843865681a97e0ad80b820.ttf
  • fontawesome-webfont-01599cb3161c59c6b712af2f1dc2412e.woff
  • analytics.js
  • roundtrip.js
  • conversion_async.js
  • 62ca3e69-1c05-44a3-ac4d-a29665c7b13b.js
  • fbds.js
  • collect
  • V7IPLBUXDVGXJDFBUYUD2Z.js
  • fbevents.hashing.js
  • out
  • out
  • out
  • out
  • out
  • out
  • out
  • u.php
  • sync
  • adsct
  • pixel
  • sd
  • 377928.gif
  • in
  • tap.php

Our browser made a total of 41 requests to load all elements on the main page. We found that 29% of them (12 requests) were addressed to the original Stanley.net, 20% (8 requests) were made to D.adroll.com and 7% (3 requests) were made to Facebook.com. The less responsive or slowest element that took the longest time to load (382 ms) belongs to the original domain Stanley.net.

Additional info on stanley.net

Requests

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

10

Javascripts

16

Images

1

CSS

27

All

Possible request optimization

1

Javascripts

5

Images

1

CSS

20

Optimized

7

All

Normal result

IP address

Stanley.net uses IP address which is currently shared with 4 other domains. The more sites share the same IP address, the higher the host server’s workload is. It is strongly recommended that the host server should be changed or the hosting provider should be requested to give a different (separate) IP address for this domain.

Poor result

IP Trace

stanley.net

hammond.net

trudel.com

tester.com

nave.com

64.99.80.121

DNS records

Type Host Target/ip TTL Other
A

stanley.net

64.99.80.121 228
NS

stanley.net

ns3.mdnsservice.com 300
NS

stanley.net

ns1.mdnsservice.com 300
NS

stanley.net

ns1.mailbank.com 300
NS

stanley.net

ns2.mdnsservice.com 300

Language and encoding

Normal result

Language

EN en language flag

Detected

N/A  language flag

Claimed

Encoding

UTF-8

Claimed

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Stanley.net 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 Stanley.net 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.

HTTPS certificate

SSL Certificate

Stanley.net has no SSL certificate. Web browsing can be safer with HTTPS connection, so we suggest that it should be obtained for this site.

Normal result

Visitor World Map

The server of Stanley.net is located in Canada, but, unfortunately, we cannot identify the countries where the visitors come from and thus it’s impossible to define if the distance can potentially affect the page load time.

Good result

Good result

Social Sharing Optimization

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

stanley.net

Share this report in social media

Analyze another website

Analyze