40.1 sec in total
1.6 sec
31.7 sec
6.9 sec
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.mobiWe 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.
record.mobi performance score
name
value
score
weighting
Value4.0 s
24/100
10%
Value9.5 s
0/100
25%
Value6.4 s
40/100
10%
Value180 ms
91/100
30%
Value0.081
94/100
15%
Value11.3 s
19/100
10%
1585 ms
732 ms
1504 ms
1502 ms
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 size can be reduced by 404.6 kB (43%)
933.2 kB
528.6 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.
Potential reduce by 380.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 380.8 kB or 89% of the original size.
Potential reduce by 11.1 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.
Potential reduce by 9.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.
Potential reduce by 3.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. Record.mobi has all CSS files already compressed.
Number of requests can be reduced by 32 (74%)
43
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.
1585 ms
bootstrap.min.css
732 ms
1664180981865main-compat.css
1504 ms
1664180981866responsive-compat.css
1502 ms
1664180981867reponsive-compat1.css
1498 ms
all.min.css
1792 ms
v4-shims.min.css
1788 ms
fonts.css
3329 ms
1664180981871cropper.css
3098 ms
26_1_29_footer.css
3098 ms
1664180972723navigation_bar_css.css
3099 ms
1664180972726chatbot_bubble.css
3186 ms
jquery.min.js
3848 ms
js
4608 ms
conversion_async.js
4608 ms
conversion.js
6067 ms
jquery.cookie.js
6077 ms
bootstrap.min.js
6121 ms
lazysizes.min.js
5937 ms
velocity.min.js
5529 ms
1664180981833popup.js
5528 ms
jquery.ui.widget.js
5527 ms
jquery.iframe-transport.js
6228 ms
jquery.fileupload.js
6118 ms
1664180981834sidebar-menu.js
5936 ms
1664180981836cropper.js
6117 ms
1664180981838upload-photo.js
6119 ms
onload.js
6226 ms
1664180972722navigation_bar.js
6226 ms
1664180972727chatbot_bubble.js
6226 ms
html2canvas.js
6075 ms
hp_script.js
6183 ms
analytics.js
4258 ms
fbevents.js
2946 ms
proxima-nova-normal-700.woff
1864 ms
proxima-nova-normal-600.woff
1863 ms
proxima-nova-normal-500.woff
1861 ms
proxima-nova-normal-400.woff
1860 ms
collect
3356 ms
1013298092648180
232 ms
collect
619 ms
ga-audiences
680 ms
marketplace-bg.jpg
768 ms
glyphicons-halflings-regular.woff
772 ms
proxima-nova-italic-400.woff
140 ms
proxima-nova-italic-500.woff
625 ms
proxima-nova-italic-600.woff
138 ms
proxima-nova-italic-700.woff
139 ms
fa-regular-400.ttf
624 ms
fa-light-300.ttf
2022 ms
fa-thin-100.ttf
2123 ms
fa-solid-900.ttf
2012 ms
footer_sprite.png
375 ms
navbar-logo-white.png
177 ms
icon_apple.png
150 ms
icon_android.png
150 ms
1664180972729chatbot_bubble.png
240 ms
record.mobi accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<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
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
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
record.mobi best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
record.mobi SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
N/A
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.
record.mobi
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: