Tools & Wizards About Us
grandlucky.co.id screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 65

    Accessibility

    Visual factors better than
    that of 30% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

grandlucky.co.id

GrandLucky

Page Load Speed

11.6 sec in total

First Response

1.9 sec

Resources Loaded

9.3 sec

Page Rendered

339 ms

grandlucky.co.id screenshot

About Website

Welcome to grandlucky.co.id homepage info - get ready to check Grand Lucky best content right away, or after learning these important things about grandlucky.co.id

Grandlucky Superstore, Kami Memang Beda

Visit grandlucky.co.id

Key Findings

We analyzed Grandlucky.co.id page load time and found that the first response time was 1.9 sec and then it took 9.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

grandlucky.co.id performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.2 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value17.0 s

0/100

10%

TBT (Total Blocking Time)

Value220 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.121

84/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

Network Requests Diagram

www.grandlucky.co.id

1905 ms

cache.skin.css

491 ms

style.css

501 ms

rsmaps.css

503 ms

settings.css

502 ms

Our browser made a total of 113 requests to load all elements on the main page. We found that 81% of them (91 requests) were addressed to the original Grandlucky.co.id, 9% (10 requests) were made to Fonts.gstatic.com and 4% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (3.3 sec) belongs to the original domain Grandlucky.co.id.

Page Optimization Overview & Recommendations

Page size can be reduced by 252.4 kB (8%)

Content Size

3.3 MB

After Optimization

3.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Grandlucky.co.id main page is 3.3 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. 75% 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. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 87.2 kB

  • Original 107.8 kB
  • After minification 105.4 kB
  • After compression 20.6 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 87.2 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 117.8 kB

  • Original 2.6 MB
  • After minification 2.5 MB

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. Grand Lucky images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 27.4 kB

  • Original 397.0 kB
  • After minification 397.0 kB
  • After compression 369.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.

CSS Optimization

-11%

Potential reduce by 19.9 kB

  • Original 187.7 kB
  • After minification 187.7 kB
  • After compression 167.8 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. Grandlucky.co.id needs all CSS files to be minified and compressed as it can save up to 19.9 kB or 11% of the original size.

Requests Breakdown

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

Requests Now

100

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.grandlucky.co.id

www.grandlucky.co.id

1905 ms

cache.skin.css

cache.skin.css

491 ms

style.css

style.css

501 ms

rsmaps.css

rsmaps.css

503 ms

settings.css

settings.css

502 ms

sfsi-style.css

sfsi-style.css

505 ms

jquery-ui-min.css

jquery-ui-min.css

507 ms

font-awesome.min.css

font-awesome.min.css

736 ms

jkreativ-icon.min.css

jkreativ-icon.min.css

749 ms

style.css

style.css

750 ms

plugin.css

plugin.css

751 ms

main.css

main.css

1003 ms

boxed.css

boxed.css

752 ms

transparent.css

transparent.css

981 ms

jmegamenu.css

jmegamenu.css

998 ms

mediaelementplayer.min.css

mediaelementplayer.min.css

999 ms

responsive.css

responsive.css

1001 ms

flat.css

flat.css

1011 ms

css

css

30 ms

app.css

app.css

1225 ms

js_composer.css

js_composer.css

1497 ms

ultimate.min.css

ultimate.min.css

1505 ms

Defaults.css

Defaults.css

1247 ms

jquery.js

jquery.js

1248 ms

jquery-migrate.min.js

jquery-migrate.min.js

1249 ms

jquery.themepunch.tools.min.js

jquery.themepunch.tools.min.js

1716 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

1746 ms

custom.js

custom.js

1531 ms

picturefill.min.js

picturefill.min.js

1531 ms

menu_functions.js

menu_functions.js

1745 ms

ultimate.min.js

ultimate.min.js

1750 ms

flip.css

flip.css

1528 ms

slide.css

slide.css

1529 ms

masonry.min.js

masonry.min.js

1728 ms

jquery.masonry.min.js

jquery.masonry.min.js

1761 ms

jquery-migrate-1.1.0.min.js

jquery-migrate-1.1.0.min.js

1761 ms

jquery-ui-min.js

jquery-ui-min.js

2012 ms

modernizr.custom.min.js

modernizr.custom.min.js

1764 ms

jquery.shuffle.min.js

jquery.shuffle.min.js

1514 ms

random-shuffle-min.js

random-shuffle-min.js

1716 ms

jquery.jcommon.js

jquery.jcommon.js

1750 ms

main.js

main.js

1750 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

1778 ms

essencialplugin.js

essencialplugin.js

1777 ms

smoothscroll.js

smoothscroll.js

1726 ms

jquery.jpageload.js

jquery.jpageload.js

1754 ms

nprogress.js

nprogress.js

1754 ms

comment-reply.min.js

comment-reply.min.js

1753 ms

jquery.sharrre.min.js

jquery.sharrre.min.js

1755 ms

fotorama.js

fotorama.js

1528 ms

bootstrap.js

bootstrap.js

1710 ms

klass.min.js

klass.min.js

1752 ms

code.photoswipe.jquery-3.0.5.1.min.js

code.photoswipe.jquery-3.0.5.1.min.js

1742 ms

jquery.jresponsive360.js

jquery.jresponsive360.js

1746 ms

jquery.jnormalblog.js

jquery.jnormalblog.js

1745 ms

jquery.jtooltip.js

jquery.jtooltip.js

1531 ms

jquery.slitslider.js

jquery.slitslider.js

1752 ms

infobubble.js

infobubble.js

1753 ms

owl.carousel.min.js

owl.carousel.min.js

1753 ms

waypoints.js

waypoints.js

1500 ms

jquery.isotope.min.js

jquery.isotope.min.js

1659 ms

jquery.jnpslider.js

jquery.jnpslider.js

1707 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

1718 ms

jquery.typer.js

jquery.typer.js

1704 ms

odometer.min.js

odometer.min.js

1732 ms

jquery.tubular.1.0.js

jquery.tubular.1.0.js

1735 ms

about.jpg

about.jpg

1001 ms

membership2.jpg

membership2.jpg

1252 ms

jquery.jlanding.js

jquery.jlanding.js

1735 ms

jscripts-ftr2-min.js

jscripts-ftr2-min.js

1739 ms

js_composer_front.js

js_composer_front.js

1918 ms

S6u9w4BMUTPHh6UVSwiPHw.woff

S6u9w4BMUTPHh6UVSwiPHw.woff

25 ms

S6u9w4BMUTPHh50XSwiPHw.woff

S6u9w4BMUTPHh50XSwiPHw.woff

39 ms

S6uyw4BMUTPHjx4wWA.woff

S6uyw4BMUTPHjx4wWA.woff

64 ms

S6u9w4BMUTPHh7USSwiPHw.woff

S6u9w4BMUTPHh7USSwiPHw.woff

74 ms

S6u8w4BMUTPHh30AXC-s.woff

S6u8w4BMUTPHh30AXC-s.woff

73 ms

S6u_w4BMUTPHjxsI5wq_Gwfr.woff

S6u_w4BMUTPHjxsI5wq_Gwfr.woff

74 ms

S6u_w4BMUTPHjxsI3wi_Gwfr.woff

S6u_w4BMUTPHjxsI3wi_Gwfr.woff

73 ms

S6u8w4BMUTPHjxsAXC-s.woff

S6u8w4BMUTPHjxsAXC-s.woff

74 ms

S6u_w4BMUTPHjxsI9w2_Gwfr.woff

S6u_w4BMUTPHjxsI9w2_Gwfr.woff

75 ms

S6u-w4BMUTPHjxsIPx-oPCQ.woff

S6u-w4BMUTPHjxsIPx-oPCQ.woff

75 ms

widgets.js

widgets.js

31 ms

sdk.js

sdk.js

38 ms

sdk.js

sdk.js

15 ms

44 ms

animations.js

animations.js

1759 ms

waypoints.min.js

waypoints.min.js

1731 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2250 ms

Defaults.svg

Defaults.svg

2254 ms

Defaults.woff

Defaults.woff

2504 ms

GrandLucky-Logo.png

GrandLucky-Logo.png

1715 ms

slideshow11.jpg

slideshow11.jpg

2938 ms

slideshow41.jpg

slideshow41.jpg

2695 ms

slideshow2.jpg

slideshow2.jpg

3111 ms

slideshow3.jpg

slideshow3.jpg

2975 ms

flat_facebook.png

flat_facebook.png

2213 ms

flat_twitter.png

flat_twitter.png

2293 ms

twitter.png

twitter.png

2256 ms

flat_instagram.png

flat_instagram.png

2504 ms

paper_@2X.png

paper_@2X.png

2755 ms

Fresh.jpg

Fresh.jpg

2928 ms

membership2.jpg

membership2.jpg

3251 ms

bot_tip_icn.png

bot_tip_icn.png

2724 ms

logo_loadinggl.png

logo_loadinggl.png

2756 ms

iframe_api

iframe_api

39 ms

www-widgetapi.js

www-widgetapi.js

5 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

26 ms

settings

settings

78 ms

large_left.png

large_left.png

1638 ms

large_right.png

large_right.png

1761 ms

button.856debeac157d9669cf51e73a08fbc93.js

button.856debeac157d9669cf51e73a08fbc93.js

2 ms

embeds

embeds

23 ms

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

tweet_button.2f70fb173b9000da126c79afe2098f02.en.html

11 ms

Accessibility Review

grandlucky.co.id accessibility score

65

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

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

High

Links do not have a discernible name

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

grandlucky.co.id best practices score

67

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

High

Browser errors were logged to the console

SEO Factors

grandlucky.co.id SEO score

75

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

High

Page is blocked from indexing

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 Grandlucky.co.id 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 Grandlucky.co.id 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

grandlucky.co.id

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