Tools & Wizards About Us
weeklytimelog.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

weeklytimelog.com

WeeklyTimelog - Automatic Time tracking for Developers.

Page Load Speed

1.5 sec in total

First Response

60 ms

Resources Loaded

1.2 sec

Page Rendered

198 ms

weeklytimelog.com screenshot

About Website

Welcome to weeklytimelog.com homepage info - get ready to check Weekly Timelog best content for Mexico right away, or after learning these important things about weeklytimelog.com

It automatically records DEVELOPER's activity while helping MANAGERS collect team's timelogs, handle booking, budget & invoicing. This is the first real automated activity tracker, that makes it easy ...

Visit weeklytimelog.com

Key Findings

We analyzed Weeklytimelog.com page load time and found that the first response time was 60 ms and then it took 1.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

weeklytimelog.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value17.4 s

0/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value1,180 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.388

26/100

15%

TTI (Time to Interactive)

Value17.2 s

4/100

10%

Network Requests Diagram

weeklytimelog.com

60 ms

weeklytimelog.com

96 ms

bootstrap.min.css

26 ms

animate.min.css

39 ms

slick.css

47 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 64% of them (47 requests) were addressed to the original Weeklytimelog.com, 8% (6 requests) were made to Fonts.gstatic.com and 7% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (648 ms) belongs to the original domain Weeklytimelog.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 510.4 kB (34%)

Content Size

1.5 MB

After Optimization

998.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Weeklytimelog.com main page is 1.5 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. 65% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 30.0 kB

  • Original 39.4 kB
  • After minification 35.9 kB
  • After compression 9.4 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 30.0 kB or 76% of the original size.

Image Optimization

-40%

Potential reduce by 442.9 kB

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

JavaScript Optimization

-13%

Potential reduce by 34.9 kB

  • Original 261.2 kB
  • After minification 261.1 kB
  • After compression 226.3 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 34.9 kB or 13% of the original size.

CSS Optimization

-3%

Potential reduce by 2.6 kB

  • Original 96.9 kB
  • After minification 96.9 kB
  • After compression 94.2 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. Weeklytimelog.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 28 (47%)

Requests Now

59

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

weeklytimelog.com

weeklytimelog.com

60 ms

weeklytimelog.com

weeklytimelog.com

96 ms

bootstrap.min.css

bootstrap.min.css

26 ms

animate.min.css

animate.min.css

39 ms

slick.css

slick.css

47 ms

font-awesome.min.css

font-awesome.min.css

55 ms

style-v7.css

style-v7.css

42 ms

custom-v7.css

custom-v7.css

54 ms

responsiveness-v7.css

responsiveness-v7.css

52 ms

zhelpers.css

zhelpers.css

63 ms

jssocials.css

jssocials.css

66 ms

jssocials-theme-flat.css

jssocials-theme-flat.css

75 ms

0P60RLUXHow

0P60RLUXHow

122 ms

email-decode.min.js

email-decode.min.js

58 ms

jquery-2.1.1.js

jquery-2.1.1.js

88 ms

pace.min.js

pace.min.js

104 ms

bootstrap.min.js

bootstrap.min.js

103 ms

classie.js

classie.js

73 ms

cbpAnimatedHeader.js

cbpAnimatedHeader.js

112 ms

wow.min.js

wow.min.js

120 ms

inspinia.js

inspinia.js

120 ms

slick.min.js

slick.min.js

121 ms

jssocials.min.js

jssocials.min.js

124 ms

install.png

install.png

209 ms

code.png

code.png

208 ms

review.png

review.png

213 ms

jira.png

jira.png

218 ms

asana.png

asana.png

218 ms

trello.png

trello.png

217 ms

youtrack.png

youtrack.png

214 ms

slack.png

slack.png

213 ms

github.png

github.png

261 ms

bitbucket.png

bitbucket.png

260 ms

gitlab.png

gitlab.png

259 ms

google-calendar.png

google-calendar.png

258 ms

google-hangout.png

google-hangout.png

258 ms

appearin.png

appearin.png

254 ms

google-drive.png

google-drive.png

314 ms

one-drive.png

one-drive.png

312 ms

location.png

location.png

294 ms

summary.png

summary.png

303 ms

css

css

41 ms

my-timelogs.png

my-timelogs.png

301 ms

demo.png

demo.png

288 ms

activity-tracked-explained.jpg

activity-tracked-explained.jpg

284 ms

overview.png

overview.png

289 ms

setup.png

setup.png

288 ms

logo_eye.png

logo_eye.png

648 ms

www-player.css

www-player.css

104 ms

www-embed-player.js

www-embed-player.js

160 ms

base.js

base.js

248 ms

graph.facebook.com

graph.facebook.com

547 ms

share

share

433 ms

analytics.js

analytics.js

153 ms

main.js

main.js

384 ms

insight.min.js

insight.min.js

382 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

524 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

152 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

519 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

522 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

523 ms

collect

collect

376 ms

asset_composer.js

asset_composer.js

423 ms

ad_status.js

ad_status.js

224 ms

insight_tag_errors.gif

insight_tag_errors.gif

392 ms

embed.js

embed.js

61 ms

graph.facebook.com

graph.facebook.com

55 ms

js

js

264 ms

share

share

242 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

10 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

9 ms

id

id

14 ms

Create

Create

23 ms

Accessibility Review

weeklytimelog.com accessibility score

68

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

Image elements do not have [alt] attributes

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

weeklytimelog.com best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

weeklytimelog.com SEO score

89

Search Engine Optimization Advices

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

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weeklytimelog.com 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 Weeklytimelog.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

weeklytimelog.com

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