Tools & Wizards About Us
w360.asia screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

w360.asia

Digital Marketing Agency & Services | W360 Group Pte Ltd

Page Load Speed

17.5 sec in total

First Response

5 sec

Resources Loaded

11.8 sec

Page Rendered

647 ms

w360.asia screenshot

About Website

Welcome to w360.asia homepage info - get ready to check W360 best content right away, or after learning these important things about w360.asia

W360 Group is the leading digital marketing agency headquartered in Singapore with unrivalled expertise and strong track record in digital marketing services.

Visit w360.asia

Key Findings

We analyzed W360.asia page load time and found that the first response time was 5 sec and then it took 12.5 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

w360.asia performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value20.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value33.2 s

0/100

25%

SI (Speed Index)

Value28.1 s

0/100

10%

TBT (Total Blocking Time)

Value1,170 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.015

100/100

15%

TTI (Time to Interactive)

Value33.8 s

0/100

10%

Network Requests Diagram

www.w360.asia

5026 ms

mediaelementplayer-legacy.min.css

18 ms

wp-mediaelement.min.css

19 ms

styles.css

681 ms

wpcf7-redirect-frontend.min.css

684 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 71% of them (78 requests) were addressed to the original W360.asia, 12% (13 requests) were made to C0.wp.com and 3% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain W360.asia.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.9 MB (63%)

Content Size

4.6 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of W360.asia main page is 4.6 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. Javascripts take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 689.1 kB

  • Original 768.7 kB
  • After minification 763.3 kB
  • After compression 79.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 689.1 kB or 90% of the original size.

Image Optimization

-1%

Potential reduce by 9.9 kB

  • Original 1.2 MB
  • After minification 1.1 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. W360 images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 1.0 MB

  • Original 1.4 MB
  • After minification 850.6 kB
  • After compression 329.6 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 1.0 MB or 76% of the original size.

CSS Optimization

-86%

Potential reduce by 1.2 MB

  • Original 1.4 MB
  • After minification 1.2 MB
  • After compression 184.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. W360.asia needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 86 (83%)

Requests Now

104

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.w360.asia

www.w360.asia

5026 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

18 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

19 ms

styles.css

styles.css

681 ms

wpcf7-redirect-frontend.min.css

wpcf7-redirect-frontend.min.css

684 ms

front.css

front.css

705 ms

general.min.css

general.min.css

925 ms

style.min.css

style.min.css

927 ms

font-awesome.min.css

font-awesome.min.css

1131 ms

uikit.min.css

uikit.min.css

1819 ms

style.css

style.css

1380 ms

frontend.min.css

frontend.min.css

1152 ms

elementor-icons.min.css

elementor-icons.min.css

1164 ms

frontend-lite.min.css

frontend-lite.min.css

1808 ms

swiper.min.css

swiper.min.css

691 ms

elementor-faq-schema.css

elementor-faq-schema.css

692 ms

iconfont.css

iconfont.css

708 ms

pr-style.css

pr-style.css

1147 ms

slick.css

slick.css

920 ms

social-share.css

social-share.css

922 ms

main.css

main.css

940 ms

general.min.css

general.min.css

1151 ms

bootstrap.css

bootstrap.css

1634 ms

bootstrap-theme.css

bootstrap-theme.css

1342 ms

wpbc-tippy-popover.css

wpbc-tippy-popover.css

1351 ms

wpbc-tippy-times.css

wpbc-tippy-times.css

1375 ms

material-design-icons.css

material-design-icons.css

1839 ms

client.css

client.css

1383 ms

calendar.css

calendar.css

1566 ms

premium-light.css

premium-light.css

1578 ms

timeline_v2.css

timeline_v2.css

1605 ms

timeline_skin_v2.css

timeline_skin_v2.css

1613 ms

css

css

31 ms

fontawesome.min.css

fontawesome.min.css

1792 ms

brands.min.css

brands.min.css

1805 ms

solid.min.css

solid.min.css

1835 ms

jquery.min.js

jquery.min.js

9 ms

jquery-migrate.min.js

jquery-migrate.min.js

8 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

12 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

12 ms

wp-polyfill.min.js

wp-polyfill.min.js

14 ms

hooks.min.js

hooks.min.js

13 ms

i18n.min.js

i18n.min.js

14 ms

i18n-loader.js

i18n-loader.js

1876 ms

wpbc_vars.js

wpbc_vars.js

1876 ms

popper.js

popper.js

2016 ms

tippy-bundle.umd.js

tippy-bundle.umd.js

2030 ms

jquery.datepick.wpbc.9.0.js

jquery.datepick.wpbc.9.0.js

2056 ms

wpbc_all.js

wpbc_all.js

2298 ms

client.js

client.js

1843 ms

create_booking.js

create_booking.js

1661 ms

wpbc_times.js

wpbc_times.js

1791 ms

url.min.js

url.min.js

3 ms

w.js

w.js

18 ms

e-202410.js

e-202410.js

18 ms

underscore.min.js

underscore.min.js

11 ms

wp-util.min.js

wp-util.min.js

10 ms

core.min.js

core.min.js

10 ms

all.min.css

all.min.css

1802 ms

v4-shims.min.css

v4-shims.min.css

1827 ms

animations.min.css

animations.min.css

1621 ms

timeline_v2.js

timeline_v2.js

1642 ms

elementor-schema.js

elementor-schema.js

1786 ms

index.js

index.js

1785 ms

index.js

index.js

1610 ms

wpcf7r-fe.js

wpcf7r-fe.js

1735 ms

slide.js

slide.js

1972 ms

script.min.js

script.min.js

1795 ms

jp-search.js

jp-search.js

1779 ms

anime.min.js

anime.min.js

1765 ms

jquery.easing.js

jquery.easing.js

1763 ms

uikit.min.js

uikit.min.js

1819 ms

load-more.js

load-more.js

2047 ms

main-script.js

main-script.js

1963 ms

general.min.js

general.min.js

2013 ms

eael-1757.js

eael-1757.js

2004 ms

akismet-frontend.js

akismet-frontend.js

1821 ms

webfontloader.js

webfontloader.js

1809 ms

webpack.runtime.min.js

webpack.runtime.min.js

1782 ms

frontend-modules.min.js

frontend-modules.min.js

2252 ms

waypoints.min.js

waypoints.min.js

2228 ms

frontend.min.js

frontend.min.js

2070 ms

gtm.js

gtm.js

430 ms

gtm.js

gtm.js

849 ms

fbevents.js

fbevents.js

370 ms

w360_logo-final-final.png

w360_logo-final-final.png

1281 ms

logo.png

logo.png

1282 ms

sme-go-digital.png

sme-go-digital.png

1280 ms

shutterstock_472567336-1024x683.jpg

shutterstock_472567336-1024x683.jpg

1407 ms

IN-TEXT-SEO-to-build-your-brand.jpg

IN-TEXT-SEO-to-build-your-brand.jpg

1864 ms

SEO-marketing-1024x576.jpg

SEO-marketing-1024x576.jpg

1408 ms

SEO-Expert-1024x576.jpg

SEO-Expert-1024x576.jpg

1408 ms

11.png

11.png

1405 ms

embed

embed

737 ms

font

font

658 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1340 ms

fa-brands-400.woff

fa-brands-400.woff

1545 ms

iconfont.ttf

iconfont.ttf

1457 ms

fa-solid-900.woff

fa-solid-900.woff

1457 ms

g.gif

g.gif

454 ms

analytics.js

analytics.js

309 ms

js

js

532 ms

js

js

542 ms

g.gif

g.gif

248 ms

css

css

237 ms

collect

collect

133 ms

collect

collect

456 ms

font

font

128 ms

font

font

171 ms

ga-audiences

ga-audiences

44 ms

Accessibility Review

w360.asia accessibility score

94

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.

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

Best Practices

w360.asia 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

w360.asia SEO score

93

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

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

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 W360.asia 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 W360.asia 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

w360.asia

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