Tools & Wizards About Us
standardrule.com screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% 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

  • 84

    SEO

    Google-friendlier than
    52% of websites

standardrule.com

Standard Rule Company | Promotional Products & Apparel | Belleville, IL: Home

Page Load Speed

13.8 sec in total

First Response

5 sec

Resources Loaded

7.1 sec

Page Rendered

1.8 sec

standardrule.com screenshot

About Website

Welcome to standardrule.com homepage info - get ready to check Standard Rule best content right away, or after learning these important things about standardrule.com

Standard Rule Company. Best selection of promotional items, apparel and corporate gifts. Let us earn your business with our 1st class service and low prices.

Visit standardrule.com

Key Findings

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

Performance Metrics

standardrule.com performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value14.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value21.6 s

0/100

25%

SI (Speed Index)

Value20.8 s

0/100

10%

TBT (Total Blocking Time)

Value970 ms

28/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value25.2 s

0/100

10%

Network Requests Diagram

www.standardrule.com

4986 ms

bootstrap.min.css

40 ms

css

39 ms

owl.carousel.min.css

81 ms

flexslider.css

118 ms

Our browser made a total of 99 requests to load all elements on the main page. We found that 84% of them (83 requests) were addressed to the original Standardrule.com, 5% (5 requests) were made to Youtube.com and 4% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5 sec) belongs to the original domain Standardrule.com.

Page Optimization Overview & Recommendations

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

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Standardrule.com main page is 1.5 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. Only a small number of websites need less resources to load. Images take 766.9 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 78.7 kB

  • Original 94.2 kB
  • After minification 86.5 kB
  • After compression 15.5 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 78.7 kB or 84% of the original size.

Image Optimization

-9%

Potential reduce by 71.6 kB

  • Original 766.9 kB
  • After minification 695.3 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. Standard Rule images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 66.3 kB

  • Original 427.1 kB
  • After minification 426.4 kB
  • After compression 360.9 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 66.3 kB or 16% of the original size.

CSS Optimization

-13%

Potential reduce by 31.9 kB

  • Original 246.2 kB
  • After minification 246.2 kB
  • After compression 214.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. Standardrule.com needs all CSS files to be minified and compressed as it can save up to 31.9 kB or 13% of the original size.

Requests Breakdown

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

Requests Now

83

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.standardrule.com

www.standardrule.com

4986 ms

bootstrap.min.css

bootstrap.min.css

40 ms

css

css

39 ms

owl.carousel.min.css

owl.carousel.min.css

81 ms

flexslider.css

flexslider.css

118 ms

all.min.css

all.min.css

538 ms

slick.css

slick.css

192 ms

lightbox.css

lightbox.css

194 ms

yamm.css

yamm.css

194 ms

jquery-ui.min.css

jquery-ui.min.css

194 ms

StyleSheet

StyleSheet

576 ms

Pic

Pic

528 ms

tVDDN6_sJlA

tVDDN6_sJlA

119 ms

jquery.min.js

jquery.min.js

521 ms

jquery-ui.min.js

jquery-ui.min.js

524 ms

migrate-3.1.0.js

migrate-3.1.0.js

518 ms

bootstrap.min.js

bootstrap.min.js

521 ms

slick.min.js

slick.min.js

522 ms

hoverIntent.min.js

hoverIntent.min.js

561 ms

superfish.min.js

superfish.min.js

562 ms

jquery.validate.min.js

jquery.validate.min.js

561 ms

lightbox.js

lightbox.js

571 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

572 ms

iframeResizer.min.js

iframeResizer.min.js

573 ms

IFrameUtils.js

IFrameUtils.js

572 ms

jquery.backstretch.min.js

jquery.backstretch.min.js

573 ms

owl.carousel.min.js

owl.carousel.min.js

574 ms

scripts.js

scripts.js

576 ms

datepicker-fr-ca.js

datepicker-fr-ca.js

575 ms

custom.js

custom.js

575 ms

highslide-full.packed.js

highslide-full.packed.js

576 ms

highslide.config.js

highslide.config.js

577 ms

highslide.css

highslide.css

599 ms

Pic

Pic

599 ms

LinkPic

LinkPic

600 ms

LinkPic

LinkPic

940 ms

LinkPic

LinkPic

599 ms

LinkPic

LinkPic

940 ms

LinkPic

LinkPic

1050 ms

QPic

QPic

994 ms

QPic

QPic

951 ms

QPic

QPic

912 ms

www-player.css

www-player.css

10 ms

www-embed-player.js

www-embed-player.js

37 ms

base.js

base.js

70 ms

QPic

QPic

871 ms

QPic

QPic

869 ms

QPic

QPic

868 ms

ad_status.js

ad_status.js

560 ms

QPic

QPic

703 ms

zsuYbLQL7cfgkPw96EIg59zP1zcoLT-EKB-9U6ATFis.js

zsuYbLQL7cfgkPw96EIg59zP1zcoLT-EKB-9U6ATFis.js

600 ms

embed.js

embed.js

113 ms

QPic

QPic

535 ms

QPic

QPic

653 ms

QPic

QPic

655 ms

QPic

QPic

653 ms

QPic

QPic

652 ms

QPic

QPic

617 ms

QPic

QPic

613 ms

QPic

QPic

616 ms

QPic

QPic

615 ms

css

css

56 ms

QPic

QPic

648 ms

QPic

QPic

648 ms

QPic

QPic

647 ms

QPic

QPic

647 ms

QPic

QPic

747 ms

QPic

QPic

748 ms

QPic

QPic

749 ms

QPic

QPic

747 ms

WEBlogPic

WEBlogPic

874 ms

WEBlogPic

WEBlogPic

896 ms

QPic

QPic

746 ms

NavThumbPic

NavThumbPic

814 ms

NavThumbPic

NavThumbPic

867 ms

NavThumbPic

NavThumbPic

847 ms

NavThumbPic

NavThumbPic

864 ms

Pic

Pic

879 ms

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf

451 ms

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf

566 ms

id

id

410 ms

Pic

Pic

842 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVcUwaEQXjM.ttf

266 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVcUwaEQXjM.ttf

267 ms

fa-regular-400.ttf

fa-regular-400.ttf

713 ms

fa-light-300.ttf

fa-light-300.ttf

675 ms

fa-thin-100.ttf

fa-thin-100.ttf

716 ms

fa-solid-900.ttf

fa-solid-900.ttf

605 ms

fa-brands-400.ttf

fa-brands-400.ttf

493 ms

footer-shadow.png

footer-shadow.png

481 ms

Create

Create

165 ms

close.png

close.png

511 ms

loading.gif

loading.gif

512 ms

prev.png

prev.png

544 ms

next.png

next.png

548 ms

GenerateIT

GenerateIT

17 ms

custom.png

custom.png

39 ms

zoomout.cur

zoomout.cur

37 ms

loader.white.gif

loader.white.gif

38 ms

Accessibility Review

standardrule.com 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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Buttons do not have an accessible name

High

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

High

Links do not have a discernible name

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.

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

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

standardrule.com SEO score

84

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

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 Standardrule.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 Standardrule.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

standardrule.com

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