Tools & Wizards About Us
ozeloffice.com screenshot

Report Summary

  • 35

    Performance

    Renders faster than
    55% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 87% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

ozeloffice.com

Ozel Office

Page Load Speed

999 ms in total

First Response

63 ms

Resources Loaded

877 ms

Page Rendered

59 ms

ozeloffice.com screenshot

About Website

Visit ozeloffice.com now to see the best up-to-date Ozel Office content and also check out these interesting facts you probably never knew about ozeloffice.com

OZEL OFFICE IS AN INTERDISCIPLINARY DESIGN FIRM CREATING SPACES, OBJECTS AND EXPERIENCES AT THE INTERSECTION OF ARCHITECTURE, TECHNOLOGY AND MEDIA.

Visit ozeloffice.com

Key Findings

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

Performance Metrics

ozeloffice.com performance score

35

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value13.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.3 s

0/100

25%

SI (Speed Index)

Value13.7 s

2/100

10%

TBT (Total Blocking Time)

Value440 ms

64/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value16.2 s

6/100

10%

Network Requests Diagram

www.ozeloffice.com

63 ms

slide-normalize-f3e05d707a08546a77c65-min.en-US.css

14 ms

azbSJ625IbwhEh4dtsltjprVDiw5SaTD47J7oCdjLOjfe0q2f4e6pUJ6wRMU5QwXFmvuFebU52SkZe9XjRgywQbDFRBcjc9hFc9-r3J7OcBRiA8XpWFR-emqiAUTdcS0jhNlOfG0jAFu-WsoShFGZAsude80Zko0ZWbCHKoySkolZP37Ociuicm0jkuzpcmCO1FUiABkZWF3jAF8OcFzdP37O1FUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCjAFu-WsoShFGZAsude80ZkoRdhXCjAFu-WsoShFGZAsude80Zko0ZWbCjWw0dA9CZamhZAoROANEZA30SaBujW48Sagyjh90jhNlOeUzjhBC-eNDifUzpcmCdhZc-AF8OcFzdPUDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlOYiaikoyjamTiY8Djhy8ZYmC-Ao1OcFzdPUaiaS0jAFu-WsoShFGZAsude80Zko0ZWbCiaiaOcBDOcu8OYiaiko1iWZ8dcwldaT8dfoDSWmyScmDSeBRZPoRdhXCiaiaOcNEZAUzZcZTjh90jhNlOYiaikoDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlJygcScmTZhyXOWFyd1wlSY4zJ68ciWsuScIlSYb7fbKP-sMMeM96MKG4fJZmIMIjMkMfH6qJxubbMs6BJMHbMZ5gE-qe.js

43 ms

css2

324 ms

legacy.js

17 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 Ozeloffice.com, 55% (12 requests) were made to Assets.squarespace.com and 18% (4 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (324 ms) relates to the external source Fonts.googleapis.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 318.6 kB (19%)

Content Size

1.7 MB

After Optimization

1.3 MB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Ozeloffice.com main page is 1.7 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. Javascripts take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 310.9 kB

  • Original 340.8 kB
  • After minification 340.6 kB
  • After compression 29.9 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 310.9 kB or 91% of the original size.

JavaScript Optimization

-1%

Potential reduce by 7.6 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 1.3 MB

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 55 B

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

Requests Breakdown

Number of requests can be reduced by 13 (72%)

Requests Now

18

After Optimization

5

  • AJAX
  • JavaScript
  • CSS

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

Network Requests Diagram

www.ozeloffice.com

www.ozeloffice.com

63 ms

slide-normalize-f3e05d707a08546a77c65-min.en-US.css

slide-normalize-f3e05d707a08546a77c65-min.en-US.css

14 ms

azbSJ625IbwhEh4dtsltjprVDiw5SaTD47J7oCdjLOjfe0q2f4e6pUJ6wRMU5QwXFmvuFebU52SkZe9XjRgywQbDFRBcjc9hFc9-r3J7OcBRiA8XpWFR-emqiAUTdcS0jhNlOfG0jAFu-WsoShFGZAsude80Zko0ZWbCHKoySkolZP37Ociuicm0jkuzpcmCO1FUiABkZWF3jAF8OcFzdP37O1FUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCjAFu-WsoShFGZAsude80ZkoRdhXCjAFu-WsoShFGZAsude80Zko0ZWbCjWw0dA9CZamhZAoROANEZA30SaBujW48Sagyjh90jhNlOeUzjhBC-eNDifUzpcmCdhZc-AF8OcFzdPUDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlOYiaikoyjamTiY8Djhy8ZYmC-Ao1OcFzdPUaiaS0jAFu-WsoShFGZAsude80Zko0ZWbCiaiaOcBDOcu8OYiaiko1iWZ8dcwldaT8dfoDSWmyScmDSeBRZPoRdhXCiaiaOcNEZAUzZcZTjh90jhNlOYiaikoDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlJygcScmTZhyXOWFyd1wlSY4zJ68ciWsuScIlSYb7fbKP-sMMeM96MKG4fJZmIMIjMkMfH6qJxubbMs6BJMHbMZ5gE-qe.js

azbSJ625IbwhEh4dtsltjprVDiw5SaTD47J7oCdjLOjfe0q2f4e6pUJ6wRMU5QwXFmvuFebU52SkZe9XjRgywQbDFRBcjc9hFc9-r3J7OcBRiA8XpWFR-emqiAUTdcS0jhNlOfG0jAFu-WsoShFGZAsude80Zko0ZWbCHKoySkolZP37Ociuicm0jkuzpcmCO1FUiABkZWF3jAF8OcFzdP37O1FUiABkZWF3jAF8ShFGZAsude80ZkoRdhXCjAFu-WsoShFGZAsude80ZkoRdhXCjAFu-WsoShFGZAsude80Zko0ZWbCjWw0dA9CZamhZAoROANEZA30SaBujW48Sagyjh90jhNlOeUzjhBC-eNDifUzpcmCdhZc-AF8OcFzdPUDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlOYiaikoyjamTiY8Djhy8ZYmC-Ao1OcFzdPUaiaS0jAFu-WsoShFGZAsude80Zko0ZWbCiaiaOcBDOcu8OYiaiko1iWZ8dcwldaT8dfoDSWmyScmDSeBRZPoRdhXCiaiaOcNEZAUzZcZTjh90jhNlOYiaikoDSWmyScmDSeBRZWFR-emqiAUTdcS0jhNlJygcScmTZhyXOWFyd1wlSY4zJ68ciWsuScIlSYb7fbKP-sMMeM96MKG4fJZmIMIjMkMfH6qJxubbMs6BJMHbMZ5gE-qe.js

43 ms

css2

css2

324 ms

legacy.js

legacy.js

17 ms

modern.js

modern.js

7 ms

extract-css-runtime-32c08c126ac3b5a277d9-min.en-US.js

extract-css-runtime-32c08c126ac3b5a277d9-min.en-US.js

15 ms

extract-css-moment-js-vendor-675f9459672cf966ca51-min.en-US.js

extract-css-moment-js-vendor-675f9459672cf966ca51-min.en-US.js

13 ms

cldr-resource-pack-a682f7ad337741eb05d6-min.en-US.js

cldr-resource-pack-a682f7ad337741eb05d6-min.en-US.js

16 ms

common-vendors-stable-f9df4447a2af25df5875-min.en-US.js

common-vendors-stable-f9df4447a2af25df5875-min.en-US.js

41 ms

common-vendors-eecad2af0a4a98e2d12e-min.en-US.js

common-vendors-eecad2af0a4a98e2d12e-min.en-US.js

47 ms

common-3addf1b8ae3542ca954e-min.en-US.js

common-3addf1b8ae3542ca954e-min.en-US.js

41 ms

slides-0c4a9b61c31ae59a5e12-min.en-US.js

slides-0c4a9b61c31ae59a5e12-min.en-US.js

41 ms

slides-7fd4392cd1d89561c45b-min.en-US.css

slides-7fd4392cd1d89561c45b-min.en-US.css

47 ms

performance-2e5b687b721ed94b30f5-min.en-US.js

performance-2e5b687b721ed94b30f5-min.en-US.js

47 ms

js

js

146 ms

js

js

53 ms

analytics.js

analytics.js

23 ms

d

d

85 ms

d

d

90 ms

d

d

109 ms

collect

collect

46 ms

Accessibility Review

ozeloffice.com accessibility score

95

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

Best Practices

ozeloffice.com 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

ozeloffice.com SEO score

93

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

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 Ozeloffice.com 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 Ozeloffice.com 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

ozeloffice.com

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