Tools & Wizards About Us

Report Summary

  • 70

    Performance

    Renders faster than
    81% of other websites

  • 93

    Accessibility

    Visual factors better than
    that of 80% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

architectureweek.com

ArchitectureWeek - No. 583 - 2014.1203

Page Load Speed

4.4 sec in total

First Response

632 ms

Resources Loaded

2 sec

Page Rendered

1.8 sec

About Website

Welcome to architectureweek.com homepage info - get ready to check Architecture Week best content for Russia right away, or after learning these important things about architectureweek.com

the world magazine of design and building, with news and features on architecture, construction, digital media, and building culture.

Visit architectureweek.com

Key Findings

We analyzed Architectureweek.com page load time and found that the first response time was 632 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

architectureweek.com performance score

70

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.6 s

93/100

10%

LCP (Largest Contentful Paint)

Value6.1 s

12/100

25%

SI (Speed Index)

Value3.8 s

85/100

10%

TBT (Total Blocking Time)

Value190 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value5.7 s

67/100

10%

Network Requests Diagram

architectureweek.com

632 ms

ns_ticker.js

506 ms

urchin.js

16 ms

AWHeader.gif

471 ms

white-1x1.gif

234 ms

Our browser made a total of 19 requests to load all elements on the main page. We found that 68% of them (13 requests) were addressed to the original Architectureweek.com, 11% (2 requests) were made to Google-analytics.com and 5% (1 request) were made to Ticker.architectureweek.com. The less responsive or slowest element that took the longest time to load (973 ms) belongs to the original domain Architectureweek.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 40.5 kB (13%)

Content Size

309.8 kB

After Optimization

269.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Architectureweek.com main page is 309.8 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. 20% of websites need less resources to load. Images take 259.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 27.6 kB

  • Original 35.4 kB
  • After minification 31.2 kB
  • After compression 7.7 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 4.2 kB, which is 12% 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 27.6 kB or 78% of the original size.

Image Optimization

-2%

Potential reduce by 6.1 kB

  • Original 259.7 kB
  • After minification 253.6 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. Architecture Week images are well optimized though.

JavaScript Optimization

-46%

Potential reduce by 6.7 kB

  • Original 14.7 kB
  • After minification 14.0 kB
  • After compression 7.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 6.7 kB or 46% of the original size.

Requests Breakdown

Number of requests can be reduced by 9 (50%)

Requests Now

18

After Optimization

9

  • AJAX
  • Images
  • JavaScript

The browser has sent 18 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Architecture Week. 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

Accessibility Review

architectureweek.com accessibility score

93

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.

Best Practices

architectureweek.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

architectureweek.com SEO score

71

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    N/A

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

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