Report Summary

  • 59

    Performance

    Renders faster than
    74% of other websites

  • 50

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 0

    Best Practices

  • 73

    SEO

    Google-friendlier than
    31% of websites

glocalrecords.com

Top - GLOCAL RECORDS

Page Load Speed

3.4 sec in total

First Response

409 ms

Resources Loaded

2.9 sec

Page Rendered

83 ms

About Website

Welcome to glocalrecords.com homepage info - get ready to check GLOCAL RECORDS best content for Japan right away, or after learning these important things about glocalrecords.com

2011年5月15日原宿にオープン。中古盤はブレイクビーツ、テクノ、ハウスといったダンス・ミュージックから、レゲエ、ワールド、ジャズまでを扱い、新譜は日本人のダンスミュージックを取り揃えている。スタッフはレーベル“RUDIMENTS”を主宰するGNTと共にKINKA、JAHTOME、風祭堅太 とアンダーグラウンドで活躍するDJたちが運営する。

Visit glocalrecords.com

Key Findings

We analyzed Glocalrecords.com page load time and found that the first response time was 409 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

glocalrecords.com performance score

59

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value4.7 s

32/100

25%

SI (Speed Index)

Value8.5 s

17/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.257

48/100

15%

TTI (Time to Interactive)

Value3.8 s

90/100

10%

Network Requests Diagram

glocalrecords.com

409 ms

glocalrecords.com

913 ms

ga.js

22 ms

index.css

206 ms

jquery.tweet.css

406 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 79% of them (11 requests) were addressed to the original Glocalrecords.com, 14% (2 requests) were made to Ssl.google-analytics.com and 7% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Glocalrecords.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 49.0 kB (27%)

Content Size

182.3 kB

After Optimization

133.3 kB

In fact, the total size of Glocalrecords.com main page is 182.3 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. Only 10% of websites need less resources to load. Images take 101.4 kB which makes up the majority of the site volume.

HTML Optimization

-50%

Potential reduce by 1.7 kB

  • Original 3.4 kB
  • After minification 3.4 kB
  • After compression 1.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 1.7 kB or 50% of the original size.

Image Optimization

-26%

Potential reduce by 26.2 kB

  • Original 101.4 kB
  • After minification 75.2 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, GLOCAL RECORDS needs image optimization as it can save up to 26.2 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-22%

Potential reduce by 14.9 kB

  • Original 69.2 kB
  • After minification 62.1 kB
  • After compression 54.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 14.9 kB or 22% of the original size.

CSS Optimization

-74%

Potential reduce by 6.1 kB

  • Original 8.2 kB
  • After minification 7.2 kB
  • After compression 2.1 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. Glocalrecords.com needs all CSS files to be minified and compressed as it can save up to 6.1 kB or 74% of the original size.

Requests Breakdown

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

Requests Now

11

After Optimization

7

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GLOCAL RECORDS. 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.

Accessibility Review

glocalrecords.com accessibility score

50

Accessibility Issues

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

SEO Factors

glocalrecords.com SEO score

73

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    JA

  • Encoding

    EUC-JP

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Glocalrecords.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it matches the claimed language. Our system also found out that Glocalrecords.com main page’s claimed encoding is euc-jp. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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