Tools & Wizards About Us
invade.co screenshot

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

invade.co

Retail Spaces, Pop-Up Spaces & Events for Retail and F&B Businesses - Invade.co

Page Load Speed

4.9 sec in total

First Response

28 ms

Resources Loaded

4.8 sec

Page Rendered

94 ms

invade.co screenshot

About Website

Welcome to invade.co homepage info - get ready to check Invade best content for Singapore right away, or after learning these important things about invade.co

Discover your retail/F&B business potential with Invade, home to signature concepts such as Artbox, Eatbox and Shilin Night Market! Book immediately in a few simple steps.

Visit invade.co

Key Findings

We analyzed Invade.co page load time and found that the first response time was 28 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

invade.co performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.0 s

48/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value20.7 s

0/100

10%

TBT (Total Blocking Time)

Value2,360 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.75

6/100

15%

TTI (Time to Interactive)

Value27.9 s

0/100

10%

Network Requests Diagram

invade.co

28 ms

invade.co

907 ms

bootstrap.min.css

759 ms

owl.carousel.css

829 ms

slick.css

777 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 63% of them (29 requests) were addressed to the original Invade.co, 26% (12 requests) were made to Fonts.gstatic.com and 9% (4 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Invade.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 29.9 kB (22%)

Content Size

138.7 kB

After Optimization

108.8 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Invade.co main page is 138.7 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. 45% of websites need less resources to load. CSS take 104.3 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 27.1 kB

  • Original 33.7 kB
  • After minification 28.7 kB
  • After compression 6.5 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 5.0 kB, which is 15% 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 27.1 kB or 81% of the original size.

JavaScript Optimization

-3%

Potential reduce by 17 B

  • Original 655 B
  • After minification 655 B
  • After compression 638 B

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

-3%

Potential reduce by 2.7 kB

  • Original 104.3 kB
  • After minification 104.3 kB
  • After compression 101.6 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. Invade.co has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 20 (63%)

Requests Now

32

After Optimization

12

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

invade.co

invade.co

28 ms

invade.co

invade.co

907 ms

bootstrap.min.css

bootstrap.min.css

759 ms

owl.carousel.css

owl.carousel.css

829 ms

slick.css

slick.css

777 ms

chosen.css

chosen.css

781 ms

css

css

38 ms

css

css

60 ms

css

css

58 ms

css

css

60 ms

app.css

app.css

788 ms

email-decode.min.js

email-decode.min.js

27 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

824 ms

bootstrap.min.js

bootstrap.min.js

1516 ms

app.js

app.js

1561 ms

chosen.jquery.js

chosen.jquery.js

1541 ms

owl.carousel.min.js

owl.carousel.min.js

1558 ms

slick.js

slick.js

1557 ms

grids.js

grids.js

1576 ms

theia-sticky-sidebar.js

theia-sticky-sidebar.js

2281 ms

lazysizes.min.js

lazysizes.min.js

2289 ms

jquery.zoom.min.js

jquery.zoom.min.js

2325 ms

custom.js

custom.js

2316 ms

gtm.js

gtm.js

106 ms

loader_img.gif

loader_img.gif

1484 ms

logo-white_update.svg

logo-white_update.svg

1510 ms

logo-pink_update.svg

logo-pink_update.svg

2207 ms

flag.svg

flag.svg

2225 ms

footer_logo.svg

footer_logo.svg

2234 ms

facebook.svg

facebook.svg

2253 ms

telegram.svg

telegram.svg

2228 ms

instagram-silhouette.svg

instagram-silhouette.svg

2264 ms

footer_email.svg

footer_email.svg

2955 ms

bizsafe.svg

bizsafe.svg

2972 ms

vEF72_JTCgwQ5ejvMV0Ox_Kg1UwJ0tKfX4zNpD8E4ASzH1r9gTuoyjkj.ttf

vEF72_JTCgwQ5ejvMV0Ox_Kg1UwJ0tKfX4zNpD8E4ASzH1r9gTuoyjkj.ttf

40 ms

vEF72_JTCgwQ5ejvMV0Ox_Kg1UwJ0tKfX4zNpD8E4ASzH1r9szuoyjkj.ttf

vEF72_JTCgwQ5ejvMV0Ox_Kg1UwJ0tKfX4zNpD8E4ASzH1r9szuoyjkj.ttf

93 ms

vEF72_JTCgwQ5ejvMV0Ox_Kg1UwJ0tKfX4zNpD8E4ASzH1r93zuoyjkj.ttf

vEF72_JTCgwQ5ejvMV0Ox_Kg1UwJ0tKfX4zNpD8E4ASzH1r93zuoyjkj.ttf

40 ms

vEF72_JTCgwQ5ejvMV0Ox_Kg1UwJ0tKfX4zNpD8E4ASzH1r9Xzyoyjkj.ttf

vEF72_JTCgwQ5ejvMV0Ox_Kg1UwJ0tKfX4zNpD8E4ASzH1r9Xzyoyjkj.ttf

41 ms

vEF72_JTCgwQ5ejvMV0Ox_Kg1UwJ0tKfX4zNpD8E4ASzH1r9Zjyoyjkj.ttf

vEF72_JTCgwQ5ejvMV0Ox_Kg1UwJ0tKfX4zNpD8E4ASzH1r9Zjyoyjkj.ttf

41 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

42 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

44 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

45 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

90 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

45 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

90 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

90 ms

Accessibility Review

invade.co accessibility score

72

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

invade.co best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

invade.co SEO score

83

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

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 Invade.co 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 Invade.co 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

invade.co

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