Tools & Wizards About Us
empirediary.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

empirediary.com

Empire Diary » Manufacturer & Supplier of Diaries & Organizers Malaysia

Page Load Speed

10 sec in total

First Response

2.2 sec

Resources Loaded

7.5 sec

Page Rendered

339 ms

empirediary.com screenshot

About Website

Visit empirediary.com now to see the best up-to-date Empire Diary content for Malaysia and also check out these interesting facts you probably never knew about empirediary.com

Empire Diary is a manufacturer of custom-made and ready-made diaries, personal organizers, notebooks, folders, folios and daily planners in Malaysia.

Visit empirediary.com

Key Findings

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

Performance Metrics

empirediary.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

13/100

10%

LCP (Largest Contentful Paint)

Value18.9 s

0/100

25%

SI (Speed Index)

Value16.1 s

0/100

10%

TBT (Total Blocking Time)

Value1,350 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value17.9 s

4/100

10%

Network Requests Diagram

empirediary.com

2171 ms

style.min.css

576 ms

style.min.css

774 ms

style.min.css

1046 ms

style.min.css

804 ms

Our browser made a total of 90 requests to load all elements on the main page. We found that 83% of them (75 requests) were addressed to the original Empirediary.com, 6% (5 requests) were made to Youtube.com and 2% (2 requests) were made to Stats.wp.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Empirediary.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 121.8 kB (12%)

Content Size

1.0 MB

After Optimization

889.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Empirediary.com main page is 1.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. 80% 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 461.3 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 93.2 kB

  • Original 113.2 kB
  • After minification 104.1 kB
  • After compression 20.0 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 93.2 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 24.4 kB

  • Original 461.3 kB
  • After minification 436.9 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. Empire Diary images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.2 kB

  • Original 297.8 kB
  • After minification 297.8 kB
  • After compression 294.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

-1%

Potential reduce by 947 B

  • Original 139.3 kB
  • After minification 139.0 kB
  • After compression 138.4 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. Empirediary.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 42 (49%)

Requests Now

86

After Optimization

44

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

empirediary.com

empirediary.com

2171 ms

style.min.css

style.min.css

576 ms

style.min.css

style.min.css

774 ms

style.min.css

style.min.css

1046 ms

style.min.css

style.min.css

804 ms

style.min.css

style.min.css

837 ms

style.min.css

style.min.css

845 ms

styles.css

styles.css

1023 ms

default.css

default.css

1072 ms

style.css

style.css

1119 ms

flatsome.css

flatsome.css

1407 ms

flatsome-shop.css

flatsome-shop.css

1127 ms

style.css

style.css

1281 ms

jquery.min.js

jquery.min.js

1566 ms

jquery-migrate.min.js

jquery-migrate.min.js

1338 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

1400 ms

add-to-cart.min.js

add-to-cart.min.js

1420 ms

js.cookie.min.js

js.cookie.min.js

1538 ms

woocommerce.min.js

woocommerce.min.js

1606 ms

s-202434.js

s-202434.js

15 ms

main.js

main.js

1681 ms

js

js

54 ms

wc-blocks.css

wc-blocks.css

1492 ms

index.js

index.js

1491 ms

index.js

index.js

1546 ms

sourcebuster.min.js

sourcebuster.min.js

1643 ms

order-attribution.min.js

order-attribution.min.js

1643 ms

flatsome-live-search.js

flatsome-live-search.js

1731 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

1732 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1734 ms

wp-polyfill.min.js

wp-polyfill.min.js

2007 ms

hoverIntent.min.js

hoverIntent.min.js

2008 ms

flatsome.js

flatsome.js

2230 ms

woocommerce.js

woocommerce.js

2042 ms

e-202434.js

e-202434.js

2 ms

packery.pkgd.min.js

packery.pkgd.min.js

2041 ms

underscore.min.js

underscore.min.js

2041 ms

wp-util.min.js

wp-util.min.js

2043 ms

add-to-cart-variation.min.js

add-to-cart-variation.min.js

2087 ms

empirediary-logo-main.png

empirediary-logo-main.png

931 ms

Lazuli-Blue_510x600-247x300.jpg

Lazuli-Blue_510x600-247x300.jpg

931 ms

Lazuli-Premium-Planner-247x300.jpg

Lazuli-Premium-Planner-247x300.jpg

932 ms

Levista-Turquoise_510x600-247x300.jpg

Levista-Turquoise_510x600-247x300.jpg

929 ms

Levista-Beige_510x600-247x300.jpg

Levista-Beige_510x600-247x300.jpg

932 ms

Stardust-Grey_510x600-247x300.jpg

Stardust-Grey_510x600-247x300.jpg

970 ms

Stardust-Hibiscus-Green-247x300.jpg

Stardust-Hibiscus-Green-247x300.jpg

1133 ms

Moru-Green_510x600-247x300.jpg

Moru-Green_510x600-247x300.jpg

1179 ms

Moru-Red_510x600-247x300.jpg

Moru-Red_510x600-247x300.jpg

1180 ms

Flexa-Neu-Brown_510x600-247x300.jpg

Flexa-Neu-Brown_510x600-247x300.jpg

1181 ms

Flexa-Neu-Army-Green_510x600-247x300.jpg

Flexa-Neu-Army-Green_510x600-247x300.jpg

1181 ms

Madani-Blue_510x600-247x300.jpg

Madani-Blue_510x600-247x300.jpg

1238 ms

Madani-Turquoise_510x600-247x300.jpg

Madani-Turquoise_510x600-247x300.jpg

1393 ms

Armany-Back_510x600-247x300.jpg

Armany-Back_510x600-247x300.jpg

1461 ms

Armany-Front_510x600-247x300.jpg

Armany-Front_510x600-247x300.jpg

1461 ms

Kejora-Green_510x600-247x300.jpg

Kejora-Green_510x600-247x300.jpg

1462 ms

Kejora-Blue_510x600-247x300.jpg

Kejora-Blue_510x600-247x300.jpg

1443 ms

Smoothkin-1_510x600-247x300.jpg

Smoothkin-1_510x600-247x300.jpg

1506 ms

DMA-106-Lacostex-blue-247x300.jpg

DMA-106-Lacostex-blue-247x300.jpg

1651 ms

empirediary-client-15.png

empirediary-client-15.png

1648 ms

empirediary-client-14.png

empirediary-client-14.png

1686 ms

U2xogogSMn0

U2xogogSMn0

144 ms

empirediary-client-13.png

empirediary-client-13.png

1634 ms

fl-icons.ttf

fl-icons.ttf

1625 ms

empirediary-client-12.png

empirediary-client-12.png

1564 ms

empirediary-client-11.png

empirediary-client-11.png

1684 ms

www-player.css

www-player.css

6 ms

www-embed-player.js

www-embed-player.js

28 ms

base.js

base.js

68 ms

empirediary-client-10.png

empirediary-client-10.png

1667 ms

empirediary-client-09.png

empirediary-client-09.png

1725 ms

empirediary-client-08.png

empirediary-client-08.png

1726 ms

ad_status.js

ad_status.js

151 ms

UCY5Klx_0fJhMytIltuKLUwnjJON9GWedkq6jjIrpW0.js

UCY5Klx_0fJhMytIltuKLUwnjJON9GWedkq6jjIrpW0.js

139 ms

embed.js

embed.js

60 ms

empirediary-client-07.png

empirediary-client-07.png

1452 ms

empirediary-client-06.png

empirediary-client-06.png

1467 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

60 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

62 ms

empirediary-client-05.png

empirediary-client-05.png

1560 ms

empirediary-client-04.png

empirediary-client-04.png

1620 ms

empirediary-client-03.png

empirediary-client-03.png

1699 ms

empirediary-client-02.png

empirediary-client-02.png

1699 ms

id

id

45 ms

empirediary-client-01.png

empirediary-client-01.png

1657 ms

Create

Create

159 ms

whatsapp_logo.svg

whatsapp_logo.svg

1483 ms

x_icon.svg

x_icon.svg

1502 ms

whatsapp_logo_gray_sm.svg

whatsapp_logo_gray_sm.svg

1566 ms

whatsapp_logo_green.svg

whatsapp_logo_green.svg

1665 ms

GenerateIT

GenerateIT

28 ms

Accessibility Review

empirediary.com accessibility score

82

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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.

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

<frame> or <iframe> elements do not have a title

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

empirediary.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Page has valid source maps

SEO Factors

empirediary.com SEO score

91

Search Engine Optimization Advices

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 Empirediary.com 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 Empirediary.com 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

empirediary.com

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