Tools & Wizards About Us
safenames.com screenshot

Report Summary

  • 34

    Performance

    Renders faster than
    54% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

safenames.com

Safenames - Global Domain Search, Registration and Protection

Page Load Speed

2.5 sec in total

First Response

302 ms

Resources Loaded

1.7 sec

Page Rendered

547 ms

safenames.com screenshot

About Website

Welcome to safenames.com homepage info - get ready to check Safenames best content for United Kingdom right away, or after learning these important things about safenames.com

Safenames has been a leading provider of global domain name registration and management services for businesses since 1999. We provide domain strategy to protect and promote our customers and brands a...

Visit safenames.com

Key Findings

We analyzed Safenames.com page load time and found that the first response time was 302 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

safenames.com performance score

34

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value10.2 s

0/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value990 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.108

87/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

safenames.com

302 ms

www.safenames.net

994 ms

WebResource.axd

6 ms

ScriptResource.axd

11 ms

ScriptResource.axd

23 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Safenames.com, 78% (46 requests) were made to Safenames.net and 7% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (994 ms) relates to the external source Safenames.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 113.1 kB (5%)

Content Size

2.1 MB

After Optimization

2.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-79%

Potential reduce by 53.5 kB

  • Original 67.8 kB
  • After minification 61.5 kB
  • After compression 14.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 53.5 kB or 79% of the original size.

Image Optimization

-3%

Potential reduce by 53.2 kB

  • Original 1.9 MB
  • After minification 1.9 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. Safenames images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 215 B

  • Original 49.7 kB
  • After minification 49.7 kB
  • After compression 49.5 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

-16%

Potential reduce by 6.2 kB

  • Original 38.0 kB
  • After minification 38.0 kB
  • After compression 31.8 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. Safenames.com needs all CSS files to be minified and compressed as it can save up to 6.2 kB or 16% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (35%)

Requests Now

52

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

safenames.com

safenames.com

302 ms

www.safenames.net

www.safenames.net

994 ms

WebResource.axd

WebResource.axd

6 ms

ScriptResource.axd

ScriptResource.axd

11 ms

ScriptResource.axd

ScriptResource.axd

23 ms

bootstrap.css

bootstrap.css

34 ms

fonts.css

fonts.css

24 ms

styles.css

styles.css

31 ms

bootstrap.js

bootstrap.js

29 ms

custom.js

custom.js

27 ms

popper.min.js

popper.min.js

25 ms

core.js

core.js

27 ms

ScriptResource.axd

ScriptResource.axd

29 ms

gtm.js

gtm.js

67 ms

hotjar-1425002.js

hotjar-1425002.js

155 ms

css2

css2

46 ms

css2

css2

79 ms

uk-flag.png

uk-flag.png

22 ms

usa-flag.png

usa-flag.png

22 ms

mag-glass-sm.svg

mag-glass-sm.svg

26 ms

safenames-logo-white.svg

safenames-logo-white.svg

22 ms

london.jpg

london.jpg

205 ms

cog.svg

cog.svg

39 ms

g4s-logo.png

g4s-logo.png

24 ms

nhsbloodandtransplant.png

nhsbloodandtransplant.png

25 ms

cushman-wakefield-logo.png

cushman-wakefield-logo.png

24 ms

gsk-logo.png

gsk-logo.png

24 ms

safe2-thin-60.svg

safe2-thin-60.svg

28 ms

monitor-thin-60.svg

monitor-thin-60.svg

26 ms

server-thin-60.svg

server-thin-60.svg

27 ms

robot-thin-60.svg

robot-thin-60.svg

30 ms

nhs-blood-logo.png

nhs-blood-logo.png

37 ms

horwath-htl-logo-white.png

horwath-htl-logo-white.png

30 ms

js

js

92 ms

ga.js

ga.js

30 ms

pxiByp8kv8JHgFVrLDz8V1g.woff

pxiByp8kv8JHgFVrLDz8V1g.woff

85 ms

pxiEyp8kv8JHgFVrFJM.woff

pxiEyp8kv8JHgFVrFJM.woff

185 ms

pxiByp8kv8JHgFVrLGT9V1g.woff

pxiByp8kv8JHgFVrLGT9V1g.woff

191 ms

pxiByp8kv8JHgFVrLEj6V1g.woff

pxiByp8kv8JHgFVrLEj6V1g.woff

203 ms

modules.e5979922753cf3b8b069.js

modules.e5979922753cf3b8b069.js

154 ms

__utm.gif

__utm.gif

103 ms

security-video-person.png

security-video-person.png

25 ms

HorwathHTLhomepage

HorwathHTLhomepage

22 ms

_Incapsula_Resource

_Incapsula_Resource

193 ms

ConsolidateYourDomainsintoOnePlatformWhyOneRegistrarisAllYouWillEverNeedhomepage

ConsolidateYourDomainsintoOnePlatformWhyOneRegistrarisAllYouWillEverNeedhomepage

86 ms

OutsmartCybercriminalsWhyYourBusinessNeedsDomainProtectionNowhomepage

OutsmartCybercriminalsWhyYourBusinessNeedsDomainProtectionNowhomepage

351 ms

EdgeNextandSafenamesPartnertoEnhanceWebsiteandAppPerformanceSecurityandEdgeComputinghomepage

EdgeNextandSafenamesPartnertoEnhanceWebsiteandAppPerformanceSecurityandEdgeComputinghomepage

54 ms

services-brochure-thumb.png

services-brochure-thumb.png

16 ms

sn-dots-background.jpg

sn-dots-background.jpg

17 ms

sn-iso9001.png

sn-iso9001.png

19 ms

sn-iso27001.png

sn-iso27001.png

21 ms

icann-logo.png

icann-logo.png

19 ms

digicertpartnerplatinumlogo.png

digicertpartnerplatinumlogo.png

22 ms

facebook-48.png

facebook-48.png

26 ms

twitter-48.png

twitter-48.png

23 ms

linkedin-48.png

linkedin-48.png

25 ms

youtube-48.png

youtube-48.png

25 ms

Search-box.js

Search-box.js

15 ms

_Incapsula_Resource

_Incapsula_Resource

4 ms

Accessibility Review

safenames.com accessibility score

78

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.

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 IDs are not unique

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

safenames.com best practices score

67

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

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

safenames.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

robots.txt is not valid

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

safenames.com

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