Tools & Wizards About Us
architecturetravelcompanion.com screenshot

Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 72

    SEO

    Google-friendlier than
    31% of websites

architecturetravelcompanion.com

Frank Lloyd Wright - Architecture Travel Companion, LLC

Page Load Speed

2.2 sec in total

First Response

77 ms

Resources Loaded

1.2 sec

Page Rendered

920 ms

architecturetravelcompanion.com screenshot

About Website

Welcome to architecturetravelcompanion.com homepage info - get ready to check Architecture Travel Companion best content right away, or after learning these important things about architecturetravelcompanion.com

We specialize in tours and storytelling engagements about Frank Lloyd Wright, American Architect. All over the US.

Visit architecturetravelcompanion.com

Key Findings

We analyzed Architecturetravelcompanion.com page load time and found that the first response time was 77 ms and then it took 2.1 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

architecturetravelcompanion.com performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value490 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

architecturetravelcompanion.com

77 ms

rs=h:1000,cg:true

486 ms

script.js

144 ms

UX.4.37.7.js

26 ms

script.js

167 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Architecturetravelcompanion.com, 96% (22 requests) were made to Img1.wsimg.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Img1.wsimg.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 982.9 kB (21%)

Content Size

4.7 MB

After Optimization

3.8 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-88%

Potential reduce by 227.9 kB

  • Original 258.8 kB
  • After minification 258.8 kB
  • After compression 30.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 227.9 kB or 88% of the original size.

Image Optimization

-11%

Potential reduce by 425.8 kB

  • Original 4.0 MB
  • After minification 3.6 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, Architecture Travel Companion needs image optimization as it can save up to 425.8 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 329.2 kB

  • Original 476.7 kB
  • After minification 476.7 kB
  • After compression 147.6 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 329.2 kB or 69% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (20%)

Requests Now

15

After Optimization

12

  • Images
  • JavaScript

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

Network Requests Diagram

architecturetravelcompanion.com

architecturetravelcompanion.com

77 ms

rs=h:1000,cg:true

rs=h:1000,cg:true

486 ms

script.js

script.js

144 ms

UX.4.37.7.js

UX.4.37.7.js

26 ms

script.js

script.js

167 ms

rs=w:1920,m

rs=w:1920,m

287 ms

rs=w:1920,m

rs=w:1920,m

606 ms

rs=w:1920,m

rs=w:1920,m

424 ms

rs=w:1920,m

rs=w:1920,m

721 ms

rs=w:1920,m

rs=w:1920,m

710 ms

rs=w:1920,m

rs=w:1920,m

595 ms

rs=w:1920,m

rs=w:1920,m

807 ms

rs=w:1920,m

rs=w:1920,m

804 ms

rs=w:1920,m

rs=w:1920,m

1095 ms

rs=w:1920,m

rs=w:1920,m

803 ms

scc-c2.min.js

scc-c2.min.js

701 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7j.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7j.woff

609 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwlxdo.woff

466 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdo.woff

483 ms

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBi8JoA.woff

QGY_z_wNahGAdqQ43RhVcIgYT2Xz5u32K3vXBi8JoA.woff

569 ms

6xK1dSBYKcSV-LCoeQqfX1RYOo3qPZ7nsDQ.woff

6xK1dSBYKcSV-LCoeQqfX1RYOo3qPZ7nsDQ.woff

568 ms

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZMkids18I.woff

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZMkids18I.woff

520 ms

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZclSds18I.woff

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZclSds18I.woff

533 ms

Accessibility Review

architecturetravelcompanion.com accessibility score

81

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

button, link, and menuitem elements do not have accessible names.

High

[role]s are not contained by their required parent element

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

architecturetravelcompanion.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

architecturetravelcompanion.com SEO score

72

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

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 Architecturetravelcompanion.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 Architecturetravelcompanion.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

architecturetravelcompanion.com

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