Tools & Wizards About Us
whylongwood.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

whylongwood.com

Admissions - Longwood University

Page Load Speed

2.7 sec in total

First Response

29 ms

Resources Loaded

1.9 sec

Page Rendered

749 ms

whylongwood.com screenshot

About Website

Welcome to whylongwood.com homepage info - get ready to check Why Longwood best content for United States right away, or after learning these important things about whylongwood.com

Visit whylongwood.com

Key Findings

We analyzed Whylongwood.com page load time and found that the first response time was 29 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

whylongwood.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

16/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value1,020 ms

26/100

30%

CLS (Cumulative Layout Shift)

Value0.163

72/100

15%

TTI (Time to Interactive)

Value15.0 s

7/100

10%

Network Requests Diagram

whylongwood.com

29 ms

81 ms

gtm.js

109 ms

fnf7pdb.js

77 ms

fonts.css

107 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Whylongwood.com, 42% (38 requests) were made to Longwood.edu and 9% (8 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (688 ms) relates to the external source Google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 204.5 kB (11%)

Content Size

1.8 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Whylongwood.com main page is 1.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 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 63.1 kB

  • Original 80.7 kB
  • After minification 68.5 kB
  • After compression 17.6 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 12.2 kB, which is 15% 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 63.1 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 5.5 kB

  • Original 1.2 MB
  • After minification 1.2 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. Why Longwood images are well optimized though.

JavaScript Optimization

-22%

Potential reduce by 51.7 kB

  • Original 234.9 kB
  • After minification 234.7 kB
  • After compression 183.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 51.7 kB or 22% of the original size.

CSS Optimization

-29%

Potential reduce by 84.3 kB

  • Original 288.6 kB
  • After minification 274.0 kB
  • After compression 204.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. Whylongwood.com needs all CSS files to be minified and compressed as it can save up to 84.3 kB or 29% of the original size.

Requests Breakdown

Number of requests can be reduced by 44 (59%)

Requests Now

74

After Optimization

30

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whylongwood.com

whylongwood.com

29 ms

81 ms

gtm.js

gtm.js

109 ms

fnf7pdb.js

fnf7pdb.js

77 ms

fonts.css

fonts.css

107 ms

melbournewebfont.css

melbournewebfont.css

41 ms

jquery.fullPage.css

jquery.fullPage.css

45 ms

2023styles-1.css

2023styles-1.css

68 ms

jquery.min.js

jquery.min.js

61 ms

jquery-migrate-3.0.1.min.js

jquery-migrate-3.0.1.min.js

52 ms

cookies.js

cookies.js

44 ms

lib.min.js

lib.min.js

72 ms

modernizr-custom.js

modernizr-custom.js

59 ms

main.js

main.js

56 ms

2023scripts.js

2023scripts.js

61 ms

bsf1jiq.css

bsf1jiq.css

105 ms

sdk.js

sdk.js

59 ms

alerts.js

alerts.js

59 ms

jquery-ui.css

jquery-ui.css

63 ms

jquery-ui.min.js

jquery-ui.min.js

70 ms

typed.js@2.0.11

typed.js@2.0.11

102 ms

D6BA47D40F99110BC.css

D6BA47D40F99110BC.css

467 ms

js

js

109 ms

js

js

376 ms

analytics.js

analytics.js

30 ms

destination

destination

55 ms

collect

collect

324 ms

collect

collect

322 ms

collect

collect

206 ms

collect

collect

205 ms

js

js

119 ms

p.css

p.css

206 ms

2023-white-logo.svg

2023-white-logo.svg

157 ms

2023_rotunda_corner.svg

2023_rotunda_corner.svg

325 ms

AdmissionsHero.jpg

AdmissionsHero.jpg

313 ms

wave-tile.png

wave-tile.png

159 ms

new-home-map-01.svg

new-home-map-01.svg

314 ms

2020-06-New-Admissions-Class.jpg

2020-06-New-Admissions-Class.jpg

335 ms

The_Game_2014_MK133r-r-1-640x640.jpg

The_Game_2014_MK133r-r-1-640x640.jpg

542 ms

affordability-icon-01.svg

affordability-icon-01.svg

175 ms

fbevents.js

fbevents.js

116 ms

up_loader.1.1.0.js

up_loader.1.1.0.js

325 ms

el.min.js

el.min.js

531 ms

events.js

events.js

529 ms

scevent.min.js

scevent.min.js

299 ms

sdk.js

sdk.js

91 ms

spx

spx

387 ms

ga-audiences

ga-audiences

688 ms

560 ms

events.js

events.js

565 ms

search.svg

search.svg

312 ms

hr.svg

hr.svg

312 ms

hero-mask.svg

hero-mask.svg

315 ms

rotunda-border.svg

rotunda-border.svg

314 ms

background-photo-texture2-(1).png

background-photo-texture2-(1).png

497 ms

Day_CV2019-(65-of-216)r-1134x756.jpg

Day_CV2019-(65-of-216)r-1134x756.jpg

532 ms

COLOR-WARS_TH2023-(363-of-542)---Medium-640x426.jpg

COLOR-WARS_TH2023-(363-of-542)---Medium-640x426.jpg

497 ms

Group-team-projects_CV2017-179-r-640x426.jpg

Group-team-projects_CV2017-179-r-640x426.jpg

496 ms

Fallcampus_CV2017-366r-r-640x426.jpg

Fallcampus_CV2017-366r-r-640x426.jpg

495 ms

facebook2024.svg

facebook2024.svg

495 ms

xtwitter2024.svg

xtwitter2024.svg

530 ms

instagram2024.svg

instagram2024.svg

529 ms

youtube2024.svg

youtube2024.svg

527 ms

d

d

313 ms

d

d

495 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

545 ms

l5zOy3UN4w=

l5zOy3UN4w=

25 ms

wb0phDdni4tIv2o951Sy9fZi35dNhVYQtDM5BaqDPjHSCJy6HIKfhv7PH5D+XnM7LdQ3jA==

wb0phDdni4tIv2o951Sy9fZi35dNhVYQtDM5BaqDPjHSCJy6HIKfhv7PH5D+XnM7LdQ3jA==

25 ms

search.png

search.png

447 ms

iframe

iframe

542 ms

siteanalyze_67106556.js

siteanalyze_67106556.js

385 ms

d

d

206 ms

d

d

180 ms

d

d

269 ms

d

d

269 ms

index.php

index.php

125 ms

emergency.xml

emergency.xml

96 ms

alert.xml

alert.xml

100 ms

notice.xml

notice.xml

119 ms

main.MTBjMzdlM2YyMA.js

main.MTBjMzdlM2YyMA.js

175 ms

sp.js

sp.js

95 ms

config.json

config.json

115 ms

saq_pxl

saq_pxl

91 ms

i

i

68 ms

pixel

pixel

60 ms

image.aspx

image.aspx

48 ms

p.gif

p.gif

21 ms

pixel

pixel

17 ms

google

google

19 ms

appnexus

appnexus

5 ms

rubicon

rubicon

4 ms

Accessibility Review

whylongwood.com accessibility score

84

Accessibility Issues

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.

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

<frame> or <iframe> elements do not have a title

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

Best Practices

whylongwood.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

whylongwood.com SEO score

80

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

Image elements do not have [alt] attributes

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 Whylongwood.com 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 Whylongwood.com 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

whylongwood.com

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