Tools & Wizards About Us
intranet.shoreline.edu screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

intranet.shoreline.edu

Intranet Home | Intranet at Shoreline Community College

Page Load Speed

3.3 sec in total

First Response

172 ms

Resources Loaded

2.4 sec

Page Rendered

729 ms

intranet.shoreline.edu screenshot

About Website

Welcome to intranet.shoreline.edu homepage info - get ready to check Intranet Shoreline best content for United States right away, or after learning these important things about intranet.shoreline.edu

Intranet daily news for Shoreline Community College as well as links to important applications, forms and resources.

Visit intranet.shoreline.edu

Key Findings

We analyzed Intranet.shoreline.edu page load time and found that the first response time was 172 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

intranet.shoreline.edu performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

10/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value9.7 s

11/100

10%

TBT (Total Blocking Time)

Value7,680 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

intranet.shoreline.edu

172 ms

intranet.shoreline.edu

380 ms

gtm.js

63 ms

bootstrap.css

280 ms

main.css

600 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 53% of them (20 requests) were addressed to the original Intranet.shoreline.edu, 13% (5 requests) were made to Pro.fontawesome.com and 8% (3 requests) were made to Script.crazyegg.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Shoreline.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 157.4 kB (43%)

Content Size

368.4 kB

After Optimization

211.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Intranet.shoreline.edu main page is 368.4 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. 60% of websites need less resources to load. Javascripts take 194.5 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 32.3 kB

  • Original 38.6 kB
  • After minification 24.1 kB
  • After compression 6.3 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 14.5 kB, which is 38% 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 32.3 kB or 84% of the original size.

Image Optimization

-5%

Potential reduce by 2.6 kB

  • Original 46.7 kB
  • After minification 44.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. Intranet Shoreline images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 121.3 kB

  • Original 194.5 kB
  • After minification 179.5 kB
  • After compression 73.3 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 121.3 kB or 62% of the original size.

CSS Optimization

-1%

Potential reduce by 1.2 kB

  • Original 88.5 kB
  • After minification 88.5 kB
  • After compression 87.3 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. Intranet.shoreline.edu has all CSS files already compressed.

Requests Breakdown

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

Requests Now

29

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

intranet.shoreline.edu

intranet.shoreline.edu

172 ms

intranet.shoreline.edu

intranet.shoreline.edu

380 ms

gtm.js

gtm.js

63 ms

bootstrap.css

bootstrap.css

280 ms

main.css

main.css

600 ms

all.css

all.css

93 ms

oustyles.css

oustyles.css

334 ms

widget-api.min.css

widget-api.min.css

42 ms

alert.css

alert.css

335 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

377 ms

modernizr-2.8.3.min.js

modernizr-2.8.3.min.js

267 ms

shoreline-data.js

shoreline-data.js

376 ms

popper.min.js

popper.min.js

318 ms

bootstrap.min.js

bootstrap.min.js

387 ms

main.js

main.js

337 ms

direct-edit.js

direct-edit.js

390 ms

grant.js

grant.js

443 ms

analytics.js

analytics.js

119 ms

8282.js

8282.js

332 ms

js

js

39 ms

collect

collect

21 ms

collect

collect

30 ms

intranet.shoreline.edu.json

intranet.shoreline.edu.json

40 ms

036b9b1280597d15cf37e7acd39c6525.js

036b9b1280597d15cf37e7acd39c6525.js

13 ms

logo-full-mobile.png

logo-full-mobile.png

1146 ms

logo-full.png

logo-full.png

119 ms

line@3x.png

line@3x.png

119 ms

starfish_logo_blue.png

starfish_logo_blue.png

117 ms

icon-canvas.png

icon-canvas.png

1134 ms

61f022c0-83d2-0136-f1e5-06659b33d47c

61f022c0-83d2-0136-f1e5-06659b33d47c

647 ms

fbevents.js

fbevents.js

703 ms

libre-franklin-v2-latin-regular.woff

libre-franklin-v2-latin-regular.woff

382 ms

libre-franklin-v2-latin-700.woff

libre-franklin-v2-latin-700.woff

382 ms

libre-franklin-v2-latin-900.woff

libre-franklin-v2-latin-900.woff

382 ms

fa-solid-900.woff

fa-solid-900.woff

649 ms

fa-regular-400.woff

fa-regular-400.woff

695 ms

fa-light-300.woff

fa-light-300.woff

738 ms

fa-brands-400.woff

fa-brands-400.woff

692 ms

Accessibility Review

intranet.shoreline.edu accessibility score

100

Accessibility Issues

Best Practices

intranet.shoreline.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

intranet.shoreline.edu SEO score

92

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Intranet.shoreline.edu can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Intranet.shoreline.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

intranet.shoreline.edu

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