Tools & Wizards About Us
drupal.arizona.edu screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

drupal.arizona.edu

Build UA branded websites using Drupal and Bootstrap | UA Quickstart

Page Load Speed

1.6 sec in total

First Response

257 ms

Resources Loaded

1.2 sec

Page Rendered

151 ms

drupal.arizona.edu screenshot

About Website

Click here to check amazing Drupal Arizona content for United States. Otherwise, check out these important facts you probably never knew about drupal.arizona.edu

UA Quickstart is a combination of Drupal 7 core, plus many additional features and modules specific to the University of Arizona. UA Quickstart also comes pre-packaged with demo content that you can m...

Visit drupal.arizona.edu

Key Findings

We analyzed Drupal.arizona.edu page load time and found that the first response time was 257 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

drupal.arizona.edu performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value12,780 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.797

5/100

15%

TTI (Time to Interactive)

Value19.6 s

2/100

10%

Network Requests Diagram

drupal.arizona.edu

257 ms

aggregator.css

171 ms

book.css

174 ms

node.css

169 ms

defaults.css

174 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that all of those requests were addressed to Drupal.arizona.edu and no external sources were called. The less responsive or slowest element that took the longest time to load (730 ms) belongs to the original domain Drupal.arizona.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 104.5 kB (70%)

Content Size

149.7 kB

After Optimization

45.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Drupal.arizona.edu main page is 149.7 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. 15% of websites need less resources to load. CSS take 86.7 kB which makes up the majority of the site volume.

HTML Optimization

-72%

Potential reduce by 5.0 kB

  • Original 6.9 kB
  • After minification 6.2 kB
  • After compression 1.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 5.0 kB or 72% of the original size.

Image Optimization

-22%

Potential reduce by 2.9 kB

  • Original 12.9 kB
  • After minification 10.1 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. Obviously, Drupal Arizona needs image optimization as it can save up to 2.9 kB or 22% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-60%

Potential reduce by 26.0 kB

  • Original 43.2 kB
  • After minification 35.9 kB
  • After compression 17.2 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 26.0 kB or 60% of the original size.

CSS Optimization

-81%

Potential reduce by 70.6 kB

  • Original 86.7 kB
  • After minification 64.9 kB
  • After compression 16.1 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. Drupal.arizona.edu needs all CSS files to be minified and compressed as it can save up to 70.6 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

26

After Optimization

7

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

drupal.arizona.edu

drupal.arizona.edu

257 ms

aggregator.css

aggregator.css

171 ms

book.css

book.css

174 ms

node.css

node.css

169 ms

defaults.css

defaults.css

174 ms

system.css

system.css

171 ms

system-menus.css

system-menus.css

172 ms

user.css

user.css

328 ms

content-module.css

content-module.css

336 ms

date.css

date.css

335 ms

jquery-ui.css

jquery-ui.css

347 ms

datepicker.css

datepicker.css

337 ms

jquery.timeentry.css

jquery.timeentry.css

339 ms

filefield.css

filefield.css

480 ms

genpass.css

genpass.css

501 ms

og.css

og.css

503 ms

forum.css

forum.css

496 ms

fieldgroup.css

fieldgroup.css

497 ms

views.css

views.css

512 ms

style.css

style.css

642 ms

nice_menus.css

nice_menus.css

645 ms

js_bd5782ddb2586dab5b2c2f2a8431f8d8.js

js_bd5782ddb2586dab5b2c2f2a8431f8d8.js

730 ms

bkg.gradient.blue.png

bkg.gradient.blue.png

93 ms

blue.header.logo.png

blue.header.logo.png

94 ms

nav.png

nav.png

92 ms

links.bg.png

links.bg.png

154 ms

bullet.png

bullet.png

150 ms

Accessibility Review

drupal.arizona.edu accessibility score

91

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

[aria-*] attributes do not match their roles

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

drupal.arizona.edu best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

drupal.arizona.edu SEO score

89

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

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 Drupal.arizona.edu 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 Drupal.arizona.edu 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

drupal.arizona.edu

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