Access stanly.edu. Home

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value610 ms

49/100

30%

CLS (Cumulative Layout Shift)

Value1.033

2/100

15%

TTI (Time to Interactive)

Value15.1 s

7/100

10%

stanly.edu

435 ms

stanly.edu

1198 ms

system.base.css

559 ms

system.menus.css

584 ms

system.messages.css

585 ms

Our browser made a total of 120 requests to load all elements on the main page. We found that 90% of them (108 requests) were addressed to the original Stanly.edu, 3% (4 requests) were made to Fonts.gstatic.com and 3% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Stanly.edu.

Content Size

15.8 MB

After Optimization

14.2 MB

In fact, the total size of Stanly.edu main page is 15.8 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. 75% 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. Images take 14.5 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 95.9 kB

Original 114.0 kB
After minification 105.7 kB
After compression 18.1 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 95.9 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 573.0 kB

Original 14.5 MB
After minification 14.0 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. Stanly images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 378.3 kB

Original 519.4 kB
After minification 372.2 kB
After compression 141.0 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 378.3 kB or 73% of the original size.

CSS Optimization

-88%

Potential reduce by 533.3 kB

Original 604.3 kB
After minification 409.0 kB
After compression 71.0 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. Stanly.edu needs all CSS files to be minified and compressed as it can save up to 533.3 kB or 88% of the original size.

Requests Now

112

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

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.

High

Links do not have a discernible name

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

High

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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/).

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

stanly.edu

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Home

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

stanly.edu

stanly.edu

system.base.css

system.menus.css

system.messages.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

stanly.edu

stanly.edu

system.base.css

system.menus.css

system.messages.css

system.theme.css

comment.css

date.css

datepicker.1.7.css

date_repeat_field.css

field.css

node.css

search.css

user.css

views.css

ctools.css

panels.css

shib_auth.css

animate.css

md-slider.css

md-slider-style.css

nice_menus.css

nice_menus_default.css

menu_minipanels.css

at.settings.style.headings.css

at.layout.css

global.base.css

global.styles.css

stanly.default.layout.css

stanly.responsive.layout.css

stanly.fonts.css

stanly.menutoggle.css

responsive.custom.css

responsive.desktop.css

css

jquery.js

jquery.once.js

drupal.js

jquery.touchwipe.js

jquery.colorbox-min.js

jquery.fancybox.js

chosen.jquery.min.js

functions.js