Tools & Wizards About Us
rm2project.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

rm2project.com

NBHS Reunion – 30 year reunion page for NBHS class of 94

Page Load Speed

4 sec in total

First Response

109 ms

Resources Loaded

3.6 sec

Page Rendered

278 ms

rm2project.com screenshot

About Website

Visit rm2project.com now to see the best up-to-date Rm 2 Project content and also check out these interesting facts you probably never knew about rm2project.com

Visit rm2project.com

Key Findings

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

Performance Metrics

rm2project.com performance score

0

Network Requests Diagram

rm2project.com

109 ms

rm2project.com

238 ms

iziModal.css

209 ms

main.css

459 ms

all.min.css

249 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 91% of them (67 requests) were addressed to the original Rm2project.com, 5% (4 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Rm2project.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 56.4 kB (7%)

Content Size

765.0 kB

After Optimization

708.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Rm2project.com main page is 765.0 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. 40% of websites need less resources to load. Javascripts take 467.7 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 49.8 kB

  • Original 62.4 kB
  • After minification 61.0 kB
  • After compression 12.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. 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 49.8 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 8.4 kB
  • After minification 8.4 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. Rm 2 Project images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 2.2 kB

  • Original 467.7 kB
  • After minification 467.7 kB
  • After compression 465.5 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. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 4.4 kB

  • Original 226.5 kB
  • After minification 226.5 kB
  • After compression 222.2 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. Rm2project.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 64 (91%)

Requests Now

70

After Optimization

6

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

rm2project.com

rm2project.com

109 ms

rm2project.com

rm2project.com

238 ms

iziModal.css

iziModal.css

209 ms

main.css

main.css

459 ms

all.min.css

all.min.css

249 ms

regular.min.css

regular.min.css

306 ms

tf-style.css

tf-style.css

319 ms

dashicons.min.css

dashicons.min.css

352 ms

events-frontend.css

events-frontend.css

441 ms

events-zoom-frontend.css

events-zoom-frontend.css

492 ms

woocommerce-layout.css

woocommerce-layout.css

510 ms

woocommerce.css

woocommerce.css

544 ms

frontend-lite.min.css

frontend-lite.min.css

554 ms

swiper.min.css

swiper.min.css

650 ms

post-16602.css

post-16602.css

678 ms

frontend-lite.min.css

frontend-lite.min.css

718 ms

post-16583.css

post-16583.css

706 ms

style.min.css

style.min.css

762 ms

theme.min.css

theme.min.css

766 ms

header-footer.min.css

header-footer.min.css

852 ms

post-16572.css

post-16572.css

874 ms

post-16575.css

post-16575.css

912 ms

ekiticons.css

ekiticons.css

962 ms

widget-styles.css

widget-styles.css

1046 ms

responsive.css

responsive.css

952 ms

css

css

54 ms

jquery.min.js

jquery.min.js

1096 ms

jquery-migrate.min.js

jquery-migrate.min.js

1085 ms

swiper.min.js

swiper.min.js

1271 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

1190 ms

add-to-cart.min.js

add-to-cart.min.js

1200 ms

js.cookie.min.js

js.cookie.min.js

1252 ms

woocommerce.min.js

woocommerce.min.js

1305 ms

widget-icon-list.min.css

widget-icon-list.min.css

1316 ms

wc-blocks.css

wc-blocks.css

1484 ms

animations.min.css

animations.min.css

1471 ms

anime.min.js

anime.min.js

1571 ms

api.js

api.js

50 ms

textanimation.js

textanimation.js

1492 ms

tf-animated.js

tf-animated.js

1354 ms

tf-main.js

tf-main.js

1377 ms

iziModal.js

iziModal.js

1385 ms

jquery.mb.YTPlayer.js

jquery.mb.YTPlayer.js

1367 ms

events-frontend.js

events-frontend.js

1357 ms

sourcebuster.min.js

sourcebuster.min.js

1354 ms

order-attribution.min.js

order-attribution.min.js

1316 ms

hello-frontend.min.js

hello-frontend.min.js

1326 ms

frontend-script.js

frontend-script.js

1380 ms

widget-scripts.js

widget-scripts.js

1384 ms

webpack.runtime.min.js

webpack.runtime.min.js

1348 ms

frontend-modules.min.js

frontend-modules.min.js

1345 ms

waypoints.min.js

waypoints.min.js

1315 ms

core.min.js

core.min.js

1325 ms

frontend.min.js

frontend.min.js

1377 ms

sticky-element.js

sticky-element.js

1249 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

1361 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

1339 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1370 ms

wp-polyfill.min.js

wp-polyfill.min.js

1309 ms

hooks.min.js

hooks.min.js

1292 ms

i18n.min.js

i18n.min.js

1364 ms

frontend.min.js

frontend.min.js

1243 ms

elements-handlers.min.js

elements-handlers.min.js

1420 ms

animate-circle.min.js

animate-circle.min.js

1344 ms

elementor.js

elementor.js

1255 ms

jquery.sticky.min.js

jquery.sticky.min.js

1356 ms

BruinsLogo.png

BruinsLogo.png

1474 ms

NBHS94Flyer-1000x1000.png

NBHS94Flyer-1000x1000.png

1760 ms

font

font

35 ms

font

font

37 ms

font

font

40 ms

font

font

45 ms

recaptcha__en.js

recaptcha__en.js

28 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

206 ms

SEO Factors

rm2project.com SEO score

0

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

rm2project.com

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