Tools & Wizards About Us
day.io screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

day.io

Day.io: Time Tracking Software, Project Planning and Timesheets

Page Load Speed

6.7 sec in total

First Response

125 ms

Resources Loaded

5.2 sec

Page Rendered

1.4 sec

day.io screenshot

About Website

Visit day.io now to see the best up-to-date Day content and also check out these interesting facts you probably never knew about day.io

Trusted by over 300,000 employees for time tracking and timesheets. Keep track of your working hours from any device with ease

Visit day.io

Key Findings

We analyzed Day.io page load time and found that the first response time was 125 ms and then it took 6.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

day.io performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

51/100

25%

SI (Speed Index)

Value7.4 s

27/100

10%

TBT (Total Blocking Time)

Value1,870 ms

9/100

30%

CLS (Cumulative Layout Shift)

Value0.493

17/100

15%

TTI (Time to Interactive)

Value14.2 s

9/100

10%

Network Requests Diagram

day.io

125 ms

gtm.js

980 ms

widget-default.css

61 ms

style.min.css

95 ms

cookie-law-info-public.css

93 ms

Our browser made a total of 98 requests to load all elements on the main page. We found that 86% of them (84 requests) were addressed to the original Day.io, 3% (3 requests) were made to Google-analytics.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.6 sec) belongs to the original domain Day.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 449.0 kB (16%)

Content Size

2.8 MB

After Optimization

2.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Day.io main page is 2.8 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 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 59.2 kB

  • Original 74.8 kB
  • After minification 74.7 kB
  • After compression 15.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 59.2 kB or 79% of the original size.

Image Optimization

-15%

Potential reduce by 388.9 kB

  • Original 2.6 MB
  • After minification 2.2 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. Obviously, Day needs image optimization as it can save up to 388.9 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 569 B

  • Original 78.7 kB
  • After minification 78.7 kB
  • After compression 78.1 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 350 B

  • Original 51.3 kB
  • After minification 51.3 kB
  • After compression 50.9 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. Day.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 48 (53%)

Requests Now

91

After Optimization

43

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

day.io

day.io

125 ms

gtm.js

gtm.js

980 ms

widget-default.css

widget-default.css

61 ms

style.min.css

style.min.css

95 ms

cookie-law-info-public.css

cookie-law-info-public.css

93 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

158 ms

fonts.css

fonts.css

147 ms

bootstrap-grid.min.css

bootstrap-grid.min.css

97 ms

main11.css

main11.css

159 ms

nouislider.min.css

nouislider.min.css

205 ms

simplelightbox.css

simplelightbox.css

204 ms

jquery-3.6.0.min.js

jquery-3.6.0.min.js

204 ms

cookie-law-info-public.js

cookie-law-info-public.js

260 ms

oit-scripts12.js

oit-scripts12.js

262 ms

js

js

1002 ms

bootstrap.bottom.css

bootstrap.bottom.css

200 ms

style19.6.css

style19.6.css

879 ms

style.css

style.css

851 ms

rtl-style.css

rtl-style.css

875 ms

cookie-law-info-table.css

cookie-law-info-table.css

852 ms

20984162.js

20984162.js

945 ms

swiper.min.js

swiper.min.js

852 ms

SmoothScroll.js

SmoothScroll.js

850 ms

global6.js

global6.js

948 ms

nouislider.min.js

nouislider.min.js

946 ms

jquery.lettering.js

jquery.lettering.js

948 ms

animation-lettering.js

animation-lettering.js

956 ms

range-slider.custom1.js

range-slider.custom1.js

950 ms

dayfooter.svg

dayfooter.svg

503 ms

united.svg

united.svg

529 ms

051-Israel.svg

051-Israel.svg

506 ms

spain.svg

spain.svg

518 ms

Brazil.svg

Brazil.svg

539 ms

preloader.jpg

preloader.jpg

512 ms

icon-user.svg

icon-user.svg

513 ms

TimeAttendance.png

TimeAttendance.png

906 ms

TimeOff.png

TimeOff.png

544 ms

checkin.png

checkin.png

683 ms

logo-cookieyes.svg

logo-cookieyes.svg

534 ms

drag.png

drag.png

295 ms

icon-checked-purple.svg

icon-checked-purple.svg

200 ms

icon-checked-green.svg

icon-checked-green.svg

295 ms

icon-checked-orange.svg

icon-checked-orange.svg

196 ms

CircularStd-Medium.woff

CircularStd-Medium.woff

112 ms

CircularStd-Book.woff

CircularStd-Book.woff

334 ms

CircularStd-Bold.woff

CircularStd-Bold.woff

355 ms

TiemposHeadline-Semibold.woff

TiemposHeadline-Semibold.woff

325 ms

analytics.js

analytics.js

282 ms

39447.js

39447.js

343 ms

20984162.js

20984162.js

714 ms

20984162.js

20984162.js

962 ms

fb.js

fb.js

1100 ms

leadflows.js

leadflows.js

1102 ms

20984162.js

20984162.js

1094 ms

collect

collect

431 ms

collect

collect

417 ms

image-39-772x515-1.jpg

image-39-772x515-1.jpg

590 ms

Mask-Group-140x140-1.png

Mask-Group-140x140-1.png

552 ms

controle_icon-1.svg

controle_icon-1.svg

348 ms

Group-134.svg

Group-134.svg

339 ms

Group-133.svg

Group-133.svg

345 ms

icon-item2-1.svg

icon-item2-1.svg

302 ms

coupon-1.svg

coupon-1.svg

334 ms

clipboard-checked-2.svg

clipboard-checked-2.svg

545 ms

Union.svg

Union.svg

543 ms

quintoandar-logo-1.svg

quintoandar-logo-1.svg

639 ms

gi-group-child-logo@2x.png

gi-group-child-logo@2x.png

544 ms

Ag%C3%AAncia_Espacial_Brasileira_logo-1.svg

Ag%C3%AAncia_Espacial_Brasileira_logo-1.svg

1285 ms

oboticario.svg

oboticario.svg

549 ms

Club_Med-1.svg

Club_Med-1.svg

816 ms

AppsFlyer-logo-1.svg

AppsFlyer-logo-1.svg

820 ms

icon-success.svg

icon-success.svg

511 ms

icon-anti-fraud.svg

icon-anti-fraud.svg

599 ms

icon-timeoff.svg

icon-timeoff.svg

636 ms

icon-item2-1.svg

icon-item2-1.svg

753 ms

icon-item2-2.svg

icon-item2-2.svg

751 ms

icon-item2-3.svg

icon-item2-3.svg

638 ms

tool1.png

tool1.png

825 ms

tool2.png

tool2.png

900 ms

adp.svg

adp.svg

897 ms

tool5.png

tool5.png

920 ms

bamboohr.svg

bamboohr.svg

974 ms

xero.svg

xero.svg

824 ms

quickbooks.svg

quickbooks.svg

1017 ms

gusto.svg

gusto.svg

1042 ms

sage.svg

sage.svg

1115 ms

app-google-play.png

app-google-play.png

918 ms

app-store.svg

app-store.svg

949 ms

sap-1.svg

sap-1.svg

952 ms

social-facebook.svg

social-facebook.svg

969 ms

social-twitter.svg

social-twitter.svg

976 ms

collect

collect

410 ms

social-linkidin.svg

social-linkidin.svg

718 ms

img3.svg

img3.svg

843 ms

img2.svg

img2.svg

1611 ms

img1.svg

img1.svg

1049 ms

__ptq.gif

__ptq.gif

135 ms

shim.latest.js

shim.latest.js

46 ms

Accessibility Review

day.io accessibility score

76

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-*] attributes do not match their roles

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

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

day.io 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

day.io SEO score

98

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 Day.io 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 Day.io 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

day.io

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