Tools & Wizards About Us
namekeeper.info screenshot

Report Summary

  • 85

    Performance

    Renders faster than
    88% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 87

    SEO

    Google-friendlier than
    65% of websites

namekeeper.info

NameKeeper | Remember names easily with your iPhone

Page Load Speed

1.1 sec in total

First Response

167 ms

Resources Loaded

654 ms

Page Rendered

291 ms

namekeeper.info screenshot

About Website

Visit namekeeper.info now to see the best up-to-date Name Keeper content and also check out these interesting facts you probably never knew about namekeeper.info

Having trouble remembering names of people you meet? Keep track and remember names of people with this smart iPhone app.

Visit namekeeper.info

Key Findings

We analyzed Namekeeper.info page load time and found that the first response time was 167 ms and then it took 945 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

namekeeper.info performance score

85

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value2.8 s

84/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

Network Requests Diagram

namekeeper.info

167 ms

gtm.js

67 ms

styles.d1347d5b81501931fb99.css

87 ms

runtime.04512a2c35585e5c1879.js

94 ms

polyfills.89761553c82c54dc52e1.js

115 ms

Our browser made a total of 18 requests to load all elements on the main page. We found that 89% of them (16 requests) were addressed to the original Namekeeper.info, 6% (1 request) were made to Googletagmanager.com and 6% (1 request) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (384 ms) belongs to the original domain Namekeeper.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 224.5 kB (20%)

Content Size

1.1 MB

After Optimization

909.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Namekeeper.info main page is 1.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. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 18.3 kB

  • Original 23.1 kB
  • After minification 22.7 kB
  • After compression 4.8 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 18.3 kB or 79% of the original size.

Image Optimization

-19%

Potential reduce by 206.2 kB

  • Original 1.1 MB
  • After minification 883.7 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, Name Keeper needs image optimization as it can save up to 206.2 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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.

Requests Breakdown

Number of requests can be reduced by 4 (24%)

Requests Now

17

After Optimization

13

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

namekeeper.info

namekeeper.info

167 ms

gtm.js

gtm.js

67 ms

styles.d1347d5b81501931fb99.css

styles.d1347d5b81501931fb99.css

87 ms

runtime.04512a2c35585e5c1879.js

runtime.04512a2c35585e5c1879.js

94 ms

polyfills.89761553c82c54dc52e1.js

polyfills.89761553c82c54dc52e1.js

115 ms

main.ac15d188ea740425fbfb.js

main.ac15d188ea740425fbfb.js

283 ms

icon.svg

icon.svg

94 ms

app-store-badge.svg

app-store-badge.svg

58 ms

iPhone%207-01main.png

iPhone%207-01main.png

307 ms

iPhone%207-02add.png

iPhone%207-02add.png

183 ms

iPhone%207-03search.png

iPhone%207-03search.png

200 ms

iPhone%207-04offline.png

iPhone%207-04offline.png

279 ms

iPhone%207-05contacts.png

iPhone%207-05contacts.png

278 ms

us.svg

us.svg

384 ms

es.svg

es.svg

327 ms

fr.svg

fr.svg

361 ms

de.svg

de.svg

350 ms

analytics.js

analytics.js

24 ms

Accessibility Review

namekeeper.info accessibility score

85

Accessibility Issues

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

Best Practices

namekeeper.info best practices score

75

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

namekeeper.info SEO score

87

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

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 Namekeeper.info 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 Namekeeper.info 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

namekeeper.info

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