Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 67

    SEO

    Google-friendlier than
    26% of websites

awayday.co

AWAYDAY - Learn. Travel. Grow.

Page Load Speed

1.8 sec in total

First Response

32 ms

Resources Loaded

1.7 sec

Page Rendered

85 ms

awayday.co screenshot

About Website

Visit awayday.co now to see the best up-to-date AWAYDAY content for Singapore and also check out these interesting facts you probably never knew about awayday.co

World's only operating system centered around medical education; connecting medical event attendees with once-in-a-lifetime experiences helping them coordinate end-to-end travel with our premier p...

Visit awayday.co

Key Findings

We analyzed Awayday.co page load time and found that the first response time was 32 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

awayday.co performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value3,070 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value15.2 s

7/100

10%

Network Requests Diagram

awayday.co

32 ms

staging.awayday.co

573 ms

kxeeim9wx9

594 ms

7cec37ca2e01b5f2.css

85 ms

daba1918524f9ce0.css

167 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Awayday.co, 82% (18 requests) were made to Staging.awayday.co and 9% (2 requests) were made to Clarity.ms. The less responsive or slowest element that took the longest time to load (985 ms) relates to the external source Staging.awayday.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 911 B (44%)

Content Size

2.0 kB

After Optimization

1.1 kB

In fact, the total size of Awayday.co main page is 2.0 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. 35% of websites need less resources to load. HTML takes 1.4 kB which makes up the majority of the site volume.

HTML Optimization

-49%

Potential reduce by 686 B

  • Original 1.4 kB
  • After minification 1.3 kB
  • After compression 725 B

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 686 B or 49% of the original size.

JavaScript Optimization

-35%

Potential reduce by 225 B

  • Original 637 B
  • After minification 637 B
  • After compression 412 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 225 B or 35% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (71%)

Requests Now

21

After Optimization

6

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

Accessibility Review

awayday.co accessibility score

33

Accessibility Issues

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

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

Best Practices

awayday.co best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

awayday.co SEO score

67

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Awayday.co can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Awayday.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

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