Tools & Wizards About Us
oswego.org screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 80

    SEO

    Google-friendlier than
    42% of websites

oswego.org

Oswego City School District

Page Load Speed

1.5 sec in total

First Response

84 ms

Resources Loaded

1.1 sec

Page Rendered

354 ms

oswego.org screenshot

About Website

Welcome to oswego.org homepage info - get ready to check Oswego best content for United States right away, or after learning these important things about oswego.org

Oswego City School District

Visit oswego.org

Key Findings

We analyzed Oswego.org page load time and found that the first response time was 84 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

oswego.org performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value300 ms

79/100

30%

CLS (Cumulative Layout Shift)

Value0.326

35/100

15%

TTI (Time to Interactive)

Value9.0 s

34/100

10%

Network Requests Diagram

oswego.org

84 ms

www.oswego.org

222 ms

main.css

81 ms

tempeditstyles.css

160 ms

slicknav.css

162 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 48% of them (38 requests) were addressed to the original Oswego.org, 18% (14 requests) were made to Cnyric.org and 15% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (413 ms) belongs to the original domain Oswego.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 277.3 kB (16%)

Content Size

1.7 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oswego.org main page is 1.7 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. 55% of websites need less resources to load. Images take 1.2 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 59.8 kB

  • Original 71.8 kB
  • After minification 60.9 kB
  • After compression 12.0 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 10.9 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 59.8 kB or 83% of the original size.

Image Optimization

-3%

Potential reduce by 35.0 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. Oswego images are well optimized though.

JavaScript Optimization

-35%

Potential reduce by 111.1 kB

  • Original 316.8 kB
  • After minification 292.0 kB
  • After compression 205.7 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 111.1 kB or 35% of the original size.

CSS Optimization

-82%

Potential reduce by 71.4 kB

  • Original 87.5 kB
  • After minification 62.5 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. Oswego.org needs all CSS files to be minified and compressed as it can save up to 71.4 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (29%)

Requests Now

59

After Optimization

42

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oswego.org

oswego.org

84 ms

www.oswego.org

www.oswego.org

222 ms

main.css

main.css

81 ms

tempeditstyles.css

tempeditstyles.css

160 ms

slicknav.css

slicknav.css

162 ms

jquery.min.js

jquery.min.js

24 ms

modernizr.min.js

modernizr.min.js

38 ms

jquery.slicknav.js

jquery.slicknav.js

164 ms

js

js

53 ms

flexslider.css

flexslider.css

93 ms

jquery.flexslider.js

jquery.flexslider.js

152 ms

element.js

element.js

43 ms

css2

css2

30 ms

css2

css2

46 ms

css2

css2

48 ms

css2

css2

17 ms

icon_schooltool.png

icon_schooltool.png

179 ms

logo_header.png

logo_header.png

192 ms

nav_cal.png

nav_cal.png

176 ms

cse.js

cse.js

187 ms

flyout_high.jpg

flyout_high.jpg

165 ms

flyout_middle.jpg

flyout_middle.jpg

165 ms

flyout_riley.jpg

flyout_riley.jpg

164 ms

flyout_fitz.jpg

flyout_fitz.jpg

177 ms

flyout_leighton.jpg

flyout_leighton.jpg

177 ms

flyout_Kingsford.jpg

flyout_Kingsford.jpg

177 ms

flyout_Minetto.jpg

flyout_Minetto.jpg

306 ms

icon_search.png

icon_search.png

206 ms

mainimage1.jpg

mainimage1.jpg

327 ms

mainimage2.jpg

mainimage2.jpg

327 ms

mainimage3.jpg

mainimage3.jpg

350 ms

mainimage4.jpg

mainimage4.jpg

362 ms

mainimage5.jpg

mainimage5.jpg

384 ms

ql_parent.png

ql_parent.png

325 ms

ql_boe.png

ql_boe.png

334 ms

ql_athletics.png

ql_athletics.png

336 ms

ql_student-reg.png

ql_student-reg.png

336 ms

ql_contact.png

ql_contact.png

356 ms

newsthumbnail.jpg

newsthumbnail.jpg

358 ms

exploreBackground.jpg

exploreBackground.jpg

413 ms

logo_footer.png

logo_footer.png

372 ms

icon_rapidID.png

icon_rapidID.png

192 ms

icon_parentsquare.png

icon_parentsquare.png

194 ms

icon_tipline.png

icon_tipline.png

195 ms

nav_food.png

nav_food.png

173 ms

nav_register.png

nav_register.png

173 ms

nav_schooltool.png

nav_schooltool.png

173 ms

nav_fb.png

nav_fb.png

196 ms

icon_m_cal.png

icon_m_cal.png

196 ms

icon_m_menu.png

icon_m_menu.png

196 ms

icon_m_register.png

icon_m_register.png

306 ms

icon_m_schooltool.png

icon_m_schooltool.png

306 ms

icon_m_fb.png

icon_m_fb.png

306 ms

icon_m_rapidid.png

icon_m_rapidid.png

302 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Ew9.woff

43 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Ew9.woff

49 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Ew9.woff

55 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu170w9.woff

112 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM70w9.woff

112 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr70w9.woff

111 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w9.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC70w9.woff

111 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3aPA.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3aPA.woff

112 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zAkw.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zAkw.woff

112 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rAkw.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rAkw.woff

146 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vAkw.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vAkw.woff

146 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nAkw.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nAkw.woff

146 ms

flexslider-icon.woff

flexslider-icon.woff

210 ms

cse_element__en.js

cse_element__en.js

35 ms

default+en.css

default+en.css

219 ms

default.css

default.css

129 ms

icon_schooltool.png

icon_schooltool.png

196 ms

icon_menus.png

icon_menus.png

175 ms

async-ads.js

async-ads.js

69 ms

branding.png

branding.png

38 ms

icon_rapidID.png

icon_rapidID.png

132 ms

icon_parentsquare.png

icon_parentsquare.png

110 ms

icon_tipline.png

icon_tipline.png

110 ms

clear.png

clear.png

13 ms

flexslider-icon.ttf

flexslider-icon.ttf

25 ms

Accessibility Review

oswego.org accessibility score

86

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

oswego.org best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

oswego.org 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

Links do not have descriptive text

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oswego.org 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 Oswego.org main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

oswego.org

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