Tools & Wizards About Us
seq.org screenshot

Report Summary

  • 28

    Performance

    Renders faster than
    48% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

seq.org

Home - Sequoia Union High School District

Page Load Speed

2.4 sec in total

First Response

386 ms

Resources Loaded

1.7 sec

Page Rendered

300 ms

seq.org screenshot

About Website

Visit seq.org now to see the best up-to-date Seq content for United States and also check out these interesting facts you probably never knew about seq.org

Home - Sequoia Union High School District

Visit seq.org

Key Findings

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

Performance Metrics

seq.org performance score

28

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value12.2 s

0/100

25%

SI (Speed Index)

Value8.0 s

21/100

10%

TBT (Total Blocking Time)

Value930 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.048

99/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

seq.org

386 ms

formMailer.css

66 ms

formBuilder_980.css

131 ms

default_980.css

142 ms

customStyles.css

135 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 74% of them (57 requests) were addressed to the original Seq.org, 12% (9 requests) were made to Google.com and 6% (5 requests) were made to Translate.googleapis.com. The less responsive or slowest element that took the longest time to load (865 ms) belongs to the original domain Seq.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 356.2 kB (20%)

Content Size

1.8 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 32.9 kB

  • Original 42.0 kB
  • After minification 39.5 kB
  • After compression 9.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 32.9 kB or 78% of the original size.

Image Optimization

-4%

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

JavaScript Optimization

-45%

Potential reduce by 162.6 kB

  • Original 358.9 kB
  • After minification 327.5 kB
  • After compression 196.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 162.6 kB or 45% of the original size.

CSS Optimization

-81%

Potential reduce by 106.8 kB

  • Original 132.1 kB
  • After minification 107.7 kB
  • After compression 25.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. Seq.org needs all CSS files to be minified and compressed as it can save up to 106.8 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 42 (56%)

Requests Now

75

After Optimization

33

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

seq.org

seq.org

386 ms

formMailer.css

formMailer.css

66 ms

formBuilder_980.css

formBuilder_980.css

131 ms

default_980.css

default_980.css

142 ms

customStyles.css

customStyles.css

135 ms

popUp.js

popUp.js

133 ms

formFunctions.js

formFunctions.js

133 ms

photoalbum.js

photoalbum.js

131 ms

photoalbum_multi.js

photoalbum_multi.js

194 ms

frontPage_slideshow.js

frontPage_slideshow.js

198 ms

trim.js

trim.js

198 ms

formBuilder_validation.js

formBuilder_validation.js

201 ms

default_980.js

default_980.js

199 ms

datePicker.js

datePicker.js

204 ms

datePicker.css

datePicker.css

258 ms

nav1.css

nav1.css

259 ms

nav1.js

nav1.js

258 ms

tables3.js

tables3.js

262 ms

tables2.css

tables2.css

263 ms

tableScroll.js

tableScroll.js

263 ms

element.js

element.js

49 ms

style_fade.css

style_fade.css

320 ms

jquery_fade.js

jquery_fade.js

390 ms

wowslider_fade.js

wowslider_fade.js

322 ms

script_blur.fade.js

script_blur.fade.js

323 ms

siteBG_10.png

siteBG_10.png

222 ms

uNavDivider.png

uNavDivider.png

65 ms

spacer.gif

spacer.gif

125 ms

icon_home.png

icon_home.png

124 ms

file_2211.jpg

file_2211.jpg

309 ms

file_2171.jpg

file_2171.jpg

304 ms

file_2172.jpg

file_2172.jpg

316 ms

file_2213.jpg

file_2213.jpg

315 ms

file_2174.jpg

file_2174.jpg

302 ms

file_2175.jpg

file_2175.jpg

318 ms

file_2212.jpg

file_2212.jpg

438 ms

file_2176.jpg

file_2176.jpg

381 ms

tile_sequitur.png

tile_sequitur.png

372 ms

tile_schoolLoop2.png

tile_schoolLoop2.png

376 ms

tile_mail2.png

tile_mail2.png

378 ms

tile_facebook7.png

tile_facebook7.png

381 ms

icon_followUs.png

icon_followUs.png

434 ms

icon_twitter.png

icon_twitter.png

438 ms

icon_facebook.png

icon_facebook.png

439 ms

badge_carlmont3.png

badge_carlmont3.png

445 ms

badge_ma2.png

badge_ma2.png

445 ms

badge_adultEd2.png

badge_adultEd2.png

498 ms

badge_woodside5.png

badge_woodside5.png

501 ms

badge_sequoia2.png

badge_sequoia2.png

503 ms

badge_redwood3.png

badge_redwood3.png

505 ms

badge_eastPalo2.png

badge_eastPalo2.png

510 ms

tcpLogo_footer.png

tcpLogo_footer.png

509 ms

translateelement.css

translateelement.css

63 ms

main.js

main.js

89 ms

cse.js

cse.js

52 ms

masthead.png

masthead.png

865 ms

nav1_BG.png

nav1_BG.png

492 ms

css

css

86 ms

element_main.js

element_main.js

54 ms

jsapi

jsapi

21 ms

default+en.css

default+en.css

37 ms

minimalist.css

minimalist.css

36 ms

default+en.I.js

default+en.I.js

36 ms

minimalist.css

minimalist.css

53 ms

specialAnnouncement_BG.png

specialAnnouncement_BG.png

267 ms

readMoreBG4.png

readMoreBG4.png

267 ms

frontQuickLinksHeaderBG.png

frontQuickLinksHeaderBG.png

275 ms

quicklink_bullet.png

quicklink_bullet.png

275 ms

translate_24dp.png

translate_24dp.png

56 ms

l

l

38 ms

cleardot.gif

cleardot.gif

48 ms

te_ctrl3.gif

te_ctrl3.gif

11 ms

async-ads.js

async-ads.js

63 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

30 ms

small-logo.png

small-logo.png

18 ms

clear.gif

clear.gif

16 ms

nav_logo114.png

nav_logo114.png

3 ms

Accessibility Review

seq.org accessibility score

79

Accessibility Issues

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.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

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

Impact

Issue

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

seq.org best practices score

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

seq.org SEO score

75

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

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

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Seq.org 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 Seq.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

seq.org

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