Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 68

    SEO

    Google-friendlier than
    28% of websites

ctr.utpjournals.press

Canadian Theatre Review | University of Toronto Press

Page Load Speed

10.5 sec in total

First Response

1.2 sec

Resources Loaded

8.7 sec

Page Rendered

571 ms

ctr.utpjournals.press screenshot

About Website

Click here to check amazing Ctr Utpjournals content for Canada. Otherwise, check out these important facts you probably never knew about ctr.utpjournals.press

The Canadian Theatre Review features thought-provoking plays and articles on current issues and trends in Canadian theatre. CTR provides the Canadian theatre community with in-depth feature articles, ...

Visit ctr.utpjournals.press

Key Findings

We analyzed Ctr.utpjournals.press page load time and found that the first response time was 1.2 sec and then it took 9.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

ctr.utpjournals.press performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

1/100

10%

LCP (Largest Contentful Paint)

Value7.4 s

4/100

25%

SI (Speed Index)

Value34.9 s

0/100

10%

TBT (Total Blocking Time)

Value41,490 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.333

34/100

15%

TTI (Time to Interactive)

Value78.7 s

0/100

10%

Network Requests Diagram

ctr.utpjournals.press

1231 ms

text.css

390 ms

lomv~article-metrics-phase2.css

66 ms

lomv~product.css

43 ms

head_1_6_1363_en.css

412 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 73% of them (74 requests) were addressed to the original Ctr.utpjournals.press, 11% (11 requests) were made to Platform.twitter.com and 3% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (5.1 sec) belongs to the original domain Ctr.utpjournals.press.

Page Optimization Overview & Recommendations

Page size can be reduced by 220.4 kB (44%)

Content Size

499.6 kB

After Optimization

279.2 kB

In fact, the total size of Ctr.utpjournals.press main page is 499.6 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. 85% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 330.0 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 153.4 kB

  • Original 169.6 kB
  • After minification 70.0 kB
  • After compression 16.2 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 99.5 kB, which is 59% 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 153.4 kB or 90% of the original size.

JavaScript Optimization

-20%

Potential reduce by 67.0 kB

  • Original 330.0 kB
  • After minification 330.0 kB
  • After compression 263.1 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 67.0 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (31%)

Requests Now

96

After Optimization

66

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

Accessibility Review

ctr.utpjournals.press accessibility score

74

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

These items highlight common accessibility best practices.

Impact

Issue

High

The document uses <meta http-equiv="refresh">

Best Practices

ctr.utpjournals.press best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

ctr.utpjournals.press SEO score

68

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 Ctr.utpjournals.press 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 Ctr.utpjournals.press 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

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