Tools & Wizards About Us
arch.guru screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

arch.guru

Bohdan Orlov - iOS Engineer & Team Lead

Page Load Speed

2.5 sec in total

First Response

249 ms

Resources Loaded

1.3 sec

Page Rendered

949 ms

arch.guru screenshot

About Website

Click here to check amazing Arch content. Otherwise, check out these important facts you probably never knew about arch.guru

I’m an iOS Engineer and Team Lead from Ukraine living in London

Visit arch.guru

Key Findings

We analyzed Arch.guru page load time and found that the first response time was 249 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

arch.guru performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

84/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

66/100

25%

SI (Speed Index)

Value2.1 s

99/100

10%

TBT (Total Blocking Time)

Value16,960 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value75.5 s

0/100

10%

Network Requests Diagram

arch.guru

249 ms

css

22 ms

architecture.cea37706.jpeg

503 ms

matrix_cut.3e4a39e7.png

530 ms

roadmap.49b00650.png

290 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 50% of them (15 requests) were addressed to the original Arch.guru, 37% (11 requests) were made to Unpkg.com and 7% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (991 ms) belongs to the original domain Arch.guru.

Page Optimization Overview & Recommendations

Page size can be reduced by 183.1 kB (6%)

Content Size

3.1 MB

After Optimization

2.9 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Arch.guru main page is 3.1 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. 30% of websites need less resources to load. Images take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 33.0 kB

  • Original 43.9 kB
  • After minification 43.9 kB
  • After compression 10.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 33.0 kB or 75% of the original size.

Image Optimization

-5%

Potential reduce by 150.1 kB

  • Original 3.0 MB
  • After minification 2.9 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. Arch images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.9 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.

Requests Breakdown

Number of requests can be reduced by 4 (19%)

Requests Now

21

After Optimization

17

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

arch.guru

arch.guru

249 ms

css

css

22 ms

architecture.cea37706.jpeg

architecture.cea37706.jpeg

503 ms

matrix_cut.3e4a39e7.png

matrix_cut.3e4a39e7.png

530 ms

roadmap.49b00650.png

roadmap.49b00650.png

290 ms

moonpig.2f00c100.png

moonpig.2f00c100.png

317 ms

chappy.3d5e0a45.png

chappy.3d5e0a45.png

501 ms

Badoo.eb4aa1d1.png

Badoo.eb4aa1d1.png

449 ms

onefinestay.a9a3bbd6.png

onefinestay.a9a3bbd6.png

887 ms

whooley.a7ef53e5.jpg

whooley.a7ef53e5.jpg

737 ms

tpt.c5af1829.png

tpt.c5af1829.png

954 ms

github.svg

github.svg

150 ms

analytics.js

analytics.js

58 ms

commons-eef92a68af65d2662677.js

commons-eef92a68af65d2662677.js

786 ms

app-a82968bad2a6fd48106f.js

app-a82968bad2a6fd48106f.js

709 ms

path---index-47fa365ed81e508460c0.js

path---index-47fa365ed81e508460c0.js

691 ms

component---src-pages-index-js-b0ec185f384382f1ca84.js

component---src-pages-index-js-b0ec185f384382f1ca84.js

915 ms

cropped.02df3f94.jpg

cropped.02df3f94.jpg

991 ms

medium.svg

medium.svg

156 ms

twitter.svg

twitter.svg

147 ms

facebook.svg

facebook.svg

174 ms

linkedin.svg

linkedin.svg

132 ms

instagram.svg

instagram.svg

92 ms

46kulbz5WjvLqJZVam_k.ttf

46kulbz5WjvLqJZVam_k.ttf

7 ms

buEzpo6gcdjy0EiZMBUG4C0f-A.ttf

buEzpo6gcdjy0EiZMBUG4C0f-A.ttf

12 ms

linkedin.svg

linkedin.svg

18 ms

github.svg

github.svg

13 ms

twitter.svg

twitter.svg

15 ms

medium.svg

medium.svg

15 ms

facebook.svg

facebook.svg

17 ms

Accessibility Review

arch.guru accessibility score

85

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.

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

Best Practices

arch.guru 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

arch.guru SEO score

92

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Arch.guru 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 Arch.guru 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

arch.guru

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