Report Summary

  • 50

    Performance

    Renders faster than
    69% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 39% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

record.mobi

Domain Marketplace - Buy Domains From Other Users | Dynadot

Page Load Speed

40.1 sec in total

First Response

1.6 sec

Resources Loaded

31.7 sec

Page Rendered

6.9 sec

record.mobi screenshot

About Website

Visit record.mobi now to see the best up-to-date Record content and also check out these interesting facts you probably never knew about record.mobi

Discover domains listed by other Dynadot users on our aftermarket. Acquire domains under a 'buy-it-now' pricing or make an offer. You can even pay for select domains through monthly installments!

Visit record.mobi

Key Findings

We analyzed Record.mobi page load time and found that the first response time was 1.6 sec and then it took 38.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

record.mobi performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

24/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value180 ms

91/100

30%

CLS (Cumulative Layout Shift)

Value0.081

94/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

1585 ms

bootstrap.min.css

732 ms

1664180981865main-compat.css

1504 ms

1664180981866responsive-compat.css

1502 ms

1664180981867reponsive-compat1.css

1498 ms

Our browser made a total of 57 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Record.mobi, 4% (2 requests) were made to Googleadservices.com and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (6.2 sec) relates to the external source Dynadot.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 404.6 kB (43%)

Content Size

933.2 kB

After Optimization

528.5 kB

In fact, the total size of Record.mobi main page is 933.2 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. HTML takes 426.4 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 380.8 kB

  • Original 426.4 kB
  • After minification 426.2 kB
  • After compression 45.7 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 380.8 kB or 89% of the original size.

Image Optimization

-16%

Potential reduce by 11.1 kB

  • Original 70.8 kB
  • After minification 59.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, Record needs image optimization as it can save up to 11.1 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-5%

Potential reduce by 9.5 kB

  • Original 177.7 kB
  • After minification 177.7 kB
  • After compression 168.3 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

-1%

Potential reduce by 3.3 kB

  • Original 258.2 kB
  • After minification 258.2 kB
  • After compression 254.9 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. Record.mobi has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 32 (74%)

Requests Now

43

After Optimization

11

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

Accessibility Review

record.mobi accessibility score

73

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Internationalization and localization

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

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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.

Best Practices

record.mobi 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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

record.mobi SEO score

85

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

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 Record.mobi 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 Record.mobi 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

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