Tools & Wizards About Us
record.mx screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

record.mx

Page Load Speed

1.6 sec in total

First Response

78 ms

Resources Loaded

1.4 sec

Page Rendered

150 ms

record.mx screenshot

About Website

Welcome to record.mx homepage info - get ready to check Record best content right away, or after learning these important things about record.mx

With Bitly Enterprise, you can create your own Branded Short Domain, which drives an increase of up to 34% in CTR when compared to bit.ly links.

Visit record.mx

Key Findings

We analyzed Record.mx page load time and found that the first response time was 78 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

record.mx performance score

0

Network Requests Diagram

branded-short-domains-powered-by-bitly

78 ms

itempropwp.css

102 ms

styles-blessed1.css

110 ms

styles.css

153 ms

jquery.js

58 ms

Our browser made a total of 66 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Record.mx, 9% (6 requests) were made to and 8% (5 requests) were made to Bitly.com. The less responsive or slowest element that took the longest time to load (368 ms) relates to the external source Seg.sharethis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (69%)

Content Size

2.0 MB

After Optimization

623.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Record.mx main page is 2.0 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. 65% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 42.9 kB

  • Original 52.3 kB
  • After minification 41.7 kB
  • After compression 9.4 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. This page needs HTML code to be minified as it can gain 10.7 kB, which is 20% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 42.9 kB or 82% of the original size.

Image Optimization

-9%

Potential reduce by 13.4 kB

  • Original 157.2 kB
  • After minification 143.8 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. Record images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 705.8 kB

  • Original 1.1 MB
  • After minification 864.8 kB
  • After compression 408.0 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 705.8 kB or 63% of the original size.

CSS Optimization

-91%

Potential reduce by 654.7 kB

  • Original 716.8 kB
  • After minification 633.7 kB
  • After compression 62.0 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.mx needs all CSS files to be minified and compressed as it can save up to 654.7 kB or 91% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (76%)

Requests Now

58

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 58 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 36 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

branded-short-domains-powered-by-bitly

branded-short-domains-powered-by-bitly

78 ms

itempropwp.css

itempropwp.css

102 ms

styles-blessed1.css

styles-blessed1.css

110 ms

styles.css

styles.css

153 ms

jquery.js

jquery.js

58 ms

jquery-migrate.min.js

jquery-migrate.min.js

101 ms

bitly-client.js

bitly-client.js

193 ms

picturefill.min.js

picturefill.min.js

192 ms

modernizr.custom.min.js

modernizr.custom.min.js

192 ms

mys2uzu.js

mys2uzu.js

231 ms

oct.js

oct.js

230 ms

conversion.js

conversion.js

191 ms

in.js

in.js

104 ms

buttons.js

buttons.js

190 ms

jquery.min.js

jquery.min.js

139 ms

bootstrap.min.js

bootstrap.min.js

190 ms

jquery.backstretch.min.js

jquery.backstretch.min.js

219 ms

perfect-scrollbar.min.js

perfect-scrollbar.min.js

220 ms

perfect-scrollbar.with-mousewheel.min.js

perfect-scrollbar.with-mousewheel.min.js

221 ms

jquery.carousel.js

jquery.carousel.js

222 ms

conversion_async.js

conversion_async.js

217 ms

scripts.js

scripts.js

223 ms

forms2.js

forms2.js

224 ms

bitly_form.js

bitly_form.js

221 ms

iframe_api

iframe_api

187 ms

wp-embed.min.js

wp-embed.min.js

100 ms

d

d

115 ms

fbevents.js

fbevents.js

39 ms

Screen-Shot-2015-08-27-at-3.42.18-PM.png

Screen-Shot-2015-08-27-at-3.42.18-PM.png

21 ms

adsct

adsct

303 ms

adsct

adsct

303 ms

114 ms

analytics.js

analytics.js

108 ms

8tmb8BLpaWYw==

8tmb8BLpaWYw==

12 ms

8DXVmznw==

8DXVmznw==

11 ms

y2ZvwGHeZac

y2ZvwGHeZac

10 ms

0OOBjex2FHHHXMcSecdMppZ5x1znkXXJTtksuuuOqa627IcdMtt8Mbu+ue+x54KNcjefI99kSBpwo981yRF1565bU33ir2znsffgC5pW7LAAA=

0OOBjex2FHHHXMcSecdMppZ5x1znkXXJTtksuuuOqa627IcdMtt8Mbu+ue+x54KNcjefI99kSBpwo981yRF1565bU33ir2znsffgC5pW7LAAA=

8 ms

9DjgY3sdhRxx1zHEnnHTKaWecdc55F1yU7ZLLrrjqmutuyHHTLbfDG7vrnvseeCjXI3nyPfZEgacKPfNckRdeeuW1N94q9s57H34AuaVuywAA

9DjgY3sdhRxx1zHEnnHTKaWecdc55F1yU7ZLLrrjqmutuyHHTLbfDG7vrnvseeCjXI3nyPfZEgacKPfNckRdeeuW1N94q9s57H34AuaVuywAA

8 ms

0OOBjex2FHHHXMcSecdMppZ5x1znkXXJTtksuuuOqa627IcdMtt8Mbu+ue+x54KNcjefI99kSBpwo981yRF1565bU33ir2znsffgC5pW7LAAA=

0OOBjex2FHHHXMcSecdMppZ5x1znkXXJTtksuuuOqa627IcdMtt8Mbu+ue+x54KNcjefI99kSBpwo981yRF1565bU33ir2znsffgC5pW7LAAA=

7 ms

gtm.js

gtm.js

253 ms

munchkin.js

munchkin.js

262 ms

297 ms

sdk.js

sdk.js

73 ms

widgets.js

widgets.js

74 ms

platform.js

platform.js

271 ms

secureAnonymousFramework

secureAnonymousFramework

71 ms

header-logo.png

header-logo.png

53 ms

trust-logos.png

trust-logos.png

216 ms

icons-mini.png

icons-mini.png

138 ms

p.gif

p.gif

320 ms

224 ms

www-widgetapi.js

www-widgetapi.js

193 ms

getForm

getForm

361 ms

getAllAppDefault.esi

getAllAppDefault.esi

137 ms

collect

collect

80 ms

121 ms

xd_arbiter.php

xd_arbiter.php

66 ms

1003400186.js

1003400186.js

72 ms

munchkin.js

munchkin.js

22 ms

visitWebPage

visitWebPage

75 ms

getSegment.php

getSegment.php

368 ms

event

event

36 ms

102 ms

XDFrame

XDFrame

104 ms

t.dhj

t.dhj

84 ms

forms2.min.js

forms2.min.js

9 ms

SEO Factors

record.mx SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Record.mx can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Record.mx 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

record.mx

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