sas.ac.uk - School of Advanced Study

Sas.ac.uk Site Title

School of Advanced Study

Sas.ac.uk Meta Description

Uniting eight research institutes and a number of centres of excellence at the University of London to form the UK's national centre for the support and promotion of academic research in the humanities

Sas.ac.uk Test Results

Sas.ac.uk Mobile Performance: 16/100

Quick overview:

Opportunities

These suggestions can help your page load faster. They don't directly affect the Performance score.

Serve images in next-gen formats. Potential savings of 6,121 KiB

Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.

Efficiently encode images. Potential savings of 1,172 KiB

Optimized images load faster and consume less cellular data. Learn more.

Eliminate render-blocking resources. Potential savings of 4,510 ms

Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.

Enable text compression. Potential savings of 306 KiB

Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.

Remove unused JavaScript. Potential savings of 191 KiB

Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.

Minify JavaScript. Potential savings of 74 KiB

Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.

Reduce initial server response time. Root document took 1,180 ms

Keep the server response time for the main document short because all other requests depend on it. Learn more.

Properly size images. Potential savings of 68 KiB

Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.

Remove unused CSS. Potential savings of 59 KiB

Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.

Diagnostics

More information about the performance of your application. These numbers don't directly affect the Performance score.

Ensure text remains visible during webfont load

Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.

Does not use passive listeners to improve scrolling performance

Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.

Avoid enormous network payloads

Total size was 8,793 KiB

Large network payloads cost users real money and are highly correlated with long load times. Learn more.

Serve static assets with an efficient cache policy

82 resources found

A long cache lifetime can speed up repeat visits to your page. Learn more.

Minimize main-thread work

6.0 s

Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more

Avoid an excessive DOM size

1,502 elements

A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.

Reduce JavaScript execution time

2.7 s

Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.

Largest Contentful Paint element

1 element found

This is the largest contentful element painted within the viewport. Learn More

Avoid chaining critical requests

51 chains found

The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.

Avoid long main-thread tasks

19 long tasks found

Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

Keep request counts low and transfer sizes small

148 requests • 8,793 KiB

To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Sas.ac.uk Mobile SEO: 92/100

Quick overview:

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Links do not have descriptive text

7 links found

Descriptive link text helps search engines understand your content. Learn more.

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.

Tap targets are not sized appropriately

94% appropriately sized tap targets

Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.

Sas.ac.uk Mobile Best Practices: 69/100

Quick overview:

General

Browser errors were logged to the console

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more

Trust and Safety

Links to cross-origin destinations are unsafe

Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.

Includes front-end JavaScript libraries with known security vulnerabilities

3 vulnerabilities detected

Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.

Does not use HTTPS

1 insecure request found

All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.

Sas.ac.uk Mobile Progressive Web App: 21/100

Quick overview:

PWA Optimized

Is not configured for a custom splash screen

A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.

Does not set a theme color for the address bar.

The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.

Manifest doesn't have a maskable icon

A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched

Does not provide a valid `apple-touch-icon`

For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.

Fast and reliable

Current page does not respond with a 200 when offline

If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.

`start_url` does not respond with a 200 when offline

A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.

Page load is not fast enough on mobile networks

Interactive at 19.9 s

A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.

Installable

Does not register a service worker that controls page and `start_url`

The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.

Web app manifest does not meet the installability requirements

Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.

Does not use HTTPS

1 insecure request found

Sas.ac.uk Mobile Accessibility: 95/100

Quick overview:

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.

ARIA input fields do not have accessible names

When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.

Navigation

These are opportunities to improve keyboard navigation in your application.

Heading elements are not in a sequentially-descending order

Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more.

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.

Links do not have a discernible name

Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.

Similar tests

www.sas.com
www.sas.net
www.sas.org
www.sas.info
www.sas.biz
www.sas.us
www.sas.mobi
www.as.ac.uk
www.sas.ac.uk
www.was.ac.uk
www.swas.ac.uk
www.wsas.ac.uk
www.eas.ac.uk
www.seas.ac.uk
www.esas.ac.uk
www.das.ac.uk
www.sdas.ac.uk
www.dsas.ac.uk
www.zas.ac.uk
www.szas.ac.uk
www.zsas.ac.uk
www.xas.ac.uk
www.sxas.ac.uk
www.xsas.ac.uk
www.aas.ac.uk
www.saas.ac.uk
www.asas.ac.uk
www.ss.ac.uk
www.sqs.ac.uk
www.saqs.ac.uk
www.sqas.ac.uk
www.sws.ac.uk
www.saws.ac.uk
www.sss.ac.uk
www.sass.ac.uk
www.ssas.ac.uk
www.szs.ac.uk
www.sazs.ac.uk
www.sa.ac.uk
www.saw.ac.uk
www.sasw.ac.uk
www.sae.ac.uk
www.sase.ac.uk
www.saes.ac.uk
www.sad.ac.uk
www.sasd.ac.uk
www.sads.ac.uk
www.saz.ac.uk
www.sasz.ac.uk
www.sax.ac.uk
www.sasx.ac.uk
www.saxs.ac.uk
www.saa.ac.uk
www.sasa.ac.uk