Tools & Wizards About Us
ourweek.io screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

ourweek.io

Ourweek - Seamless way to see your google sheet events in your favorite calendar app

Page Load Speed

2.9 sec in total

First Response

67 ms

Resources Loaded

2 sec

Page Rendered

841 ms

ourweek.io screenshot

About Website

Welcome to ourweek.io homepage info - get ready to check Ourweek best content right away, or after learning these important things about ourweek.io

Organize calendar events inside from your Google Sheets documents and easily synchronize them to your favorite calendar app on any device using ourweek

Visit ourweek.io

Key Findings

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

Performance Metrics

ourweek.io performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value8.8 s

1/100

25%

SI (Speed Index)

Value2.9 s

94/100

10%

TBT (Total Blocking Time)

Value200 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.037

100/100

15%

TTI (Time to Interactive)

Value7.6 s

46/100

10%

Network Requests Diagram

ourweek.io

67 ms

ourweek.io

1033 ms

style.css

120 ms

swiper.min.css

139 ms

js

180 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 75% of them (38 requests) were addressed to the original Ourweek.io, 8% (4 requests) were made to Unpkg.com and 6% (3 requests) were made to . The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Ourweek.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 75.7 kB (25%)

Content Size

308.2 kB

After Optimization

232.4 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ourweek.io main page is 308.2 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. 70% of websites need less resources to load. Images take 286.2 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 16.3 kB

  • Original 21.3 kB
  • After minification 18.5 kB
  • After compression 5.1 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 2.8 kB, which is 13% 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 16.3 kB or 76% of the original size.

Image Optimization

-21%

Potential reduce by 59.4 kB

  • Original 286.2 kB
  • After minification 226.7 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, Ourweek needs image optimization as it can save up to 59.4 kB or 21% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

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.

Requests Breakdown

Number of requests can be reduced by 14 (34%)

Requests Now

41

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ourweek.io

ourweek.io

67 ms

ourweek.io

ourweek.io

1033 ms

style.css

style.css

120 ms

swiper.min.css

swiper.min.css

139 ms

js

js

180 ms

email-decode.min.js

email-decode.min.js

89 ms

jquery-3.3.1.slim.min.js

jquery-3.3.1.slim.min.js

117 ms

popper.min.js

popper.min.js

156 ms

bootstrap.min.js

bootstrap.min.js

148 ms

swiper.min.js

swiper.min.js

131 ms

app.js

app.js

106 ms

6895265.js

6895265.js

204 ms

bootstrap.min.css

bootstrap.min.css

116 ms

swiper.min.css

swiper.min.css

12 ms

swiper.min.js

swiper.min.js

12 ms

logo-color.svg

logo-color.svg

153 ms

hero-top.svg

hero-top.svg

153 ms

hero-bottom.svg

hero-bottom.svg

150 ms

hero-right.svg

hero-right.svg

363 ms

hero.png

hero.png

446 ms

bullet.svg

bullet.svg

196 ms

section-1-top-left.svg

section-1-top-left.svg

198 ms

section-1-top-right.svg

section-1-top-right.svg

205 ms

section-1-content.png

section-1-content.png

328 ms

section-2-bottom.svg

section-2-bottom.svg

344 ms

section-2-content.png

section-2-content.png

397 ms

section-3-top-left.svg

section-3-top-left.svg

399 ms

section-3-top-right.svg

section-3-top-right.svg

429 ms

bullet-black.svg

bullet-black.svg

432 ms

section-3-bottom-right.svg

section-3-bottom-right.svg

431 ms

section-3-content.png

section-3-content.png

433 ms

section-4-left.svg

section-4-left.svg

434 ms

section-4-content.png

section-4-content.png

460 ms

section-5-right.svg

section-5-right.svg

452 ms

section-5-bottom.svg

section-5-bottom.svg

462 ms

section-5-content.png

section-5-content.png

462 ms

feature-1.svg

feature-1.svg

463 ms

feature-2.svg

feature-2.svg

478 ms

feature-3.svg

feature-3.svg

474 ms

feature-4.svg

feature-4.svg

511 ms

section-7-left.svg

section-7-left.svg

510 ms

section-7-right.svg

section-7-right.svg

476 ms

section-contact.svg

section-contact.svg

522 ms

faq-icon.svg

faq-icon.svg

525 ms

footer-icon-bottom.svg

footer-icon-bottom.svg

527 ms

footer-icon-top.svg

footer-icon-top.svg

552 ms

logo-white.svg

logo-white.svg

577 ms

hotjar-1619976.js

hotjar-1619976.js

160 ms

+9a+wAAA==

+9a+wAAA==

8 ms

AAIrsQNGditEsBEgRboAEAEbAAIrsQNGditEWbAUKwA=

AAIrsQNGditEsBEgRboAEAEbAAIrsQNGditEWbAUKwA=

7 ms

n8dYiF7EBBmfiSky2RElMl0SFVIuiFOkkj8ayPQbqOpOKQA=

n8dYiF7EBBmfiSky2RElMl0SFVIuiFOkkj8ayPQbqOpOKQA=

5 ms

Accessibility Review

ourweek.io accessibility score

75

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.

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 IDs are not unique

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

Form elements do not have associated labels

Best Practices

ourweek.io best practices score

75

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

ourweek.io SEO score

92

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

    N/A

  • Encoding

    UTF8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ourweek.io 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 Ourweek.io main page’s claimed encoding is utf8. 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

ourweek.io

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