11.9 sec in total
2.8 sec
8.7 sec
355 ms
Visit irec.ph now to see the best up-to-date IREC content and also check out these interesting facts you probably never knew about irec.ph
International Recreation Corporation (iREC) has decades of experience in manufacturing playground equipment for play areas. We build with quality, safety and fun.
Visit irec.phWe analyzed Irec.ph page load time and found that the first response time was 2.8 sec and then it took 9.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
irec.ph performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value6.0 s
13/100
25%
Value21.1 s
0/100
10%
Value600 ms
49/100
30%
Value0.407
24/100
15%
Value16.7 s
5/100
10%
2831 ms
79 ms
152 ms
211 ms
217 ms
Our browser made a total of 95 requests to load all elements on the main page. We found that 85% of them (81 requests) were addressed to the original Irec.ph, 11% (10 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Irec.ph.
Page size can be reduced by 302.9 kB (14%)
2.1 MB
1.8 MB
In fact, the total size of Irec.ph main page is 2.1 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. 65% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 78.7 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 80% of the original size.
Potential reduce by 36.0 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. IREC images are well optimized though.
Potential reduce by 68.8 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 68.8 kB or 15% of the original size.
Potential reduce by 119.4 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. Irec.ph needs all CSS files to be minified and compressed as it can save up to 119.4 kB or 68% of the original size.
Number of requests can be reduced by 58 (73%)
79
21
The browser has sent 79 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IREC. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 41 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
www.irec.ph
2831 ms
wp-emoji-release.min.js
79 ms
gtranslate-style24.css
152 ms
styles.css
211 ms
skin.css
217 ms
jvcf7_validate.css
222 ms
wonderplugingridgalleryengine.css
219 ms
lightbox.min.css
218 ms
style.css
223 ms
font-awesome.min.css
284 ms
jquery-ui.min.css
288 ms
bootstrap.css
386 ms
jquery.mmenu.all.css
289 ms
the-core-style.css
640 ms
style.css
316 ms
prettyPhoto.css
351 ms
animate.css
354 ms
background.css
358 ms
css
38 ms
n2-ss-2.css
391 ms
jquery.js
554 ms
jquery-migrate.min.js
422 ms
flowplayer.min.js
634 ms
wonderplugingridlightbox.js
523 ms
wonderplugingridgallery.js
463 ms
modernizr.min.js
489 ms
bootstrap.min.js
540 ms
jquery.touchSwipe.min.js
557 ms
html5shiv.js
593 ms
respond.min.js
613 ms
js
70 ms
n2.js
735 ms
nextend-gsap.min.js
801 ms
nextend-frontend.min.js
800 ms
smartslider-frontend.min.js
856 ms
smartslider-simple-type-frontend.min.js
749 ms
nextend-webfontloader.min.js
749 ms
n2-ss-2.js
815 ms
element.js
67 ms
jquery.validate.min.js
814 ms
jquery.jvcf7_validation.js
747 ms
wp-lightbox-2.min.js
712 ms
custom.js
654 ms
wp-gallery-custom-links.js
665 ms
imagesloaded.min.js
664 ms
jquery.carouFredSel-6.2.1-packed.js
665 ms
jquery.prettyPhoto.js
678 ms
jquery.customInput.js
758 ms
scrollTo.min.js
693 ms
jquery.mmenu.min.all.js
685 ms
selectize.min.js
686 ms
jquery.parallax.js
665 ms
effect.min.js
627 ms
lazysizes.min.js
856 ms
general.js
859 ms
core.js
829 ms
transition.js
865 ms
background.js
820 ms
background.init.js
796 ms
wp-embed.min.js
766 ms
css
18 ms
icon_indoorplay.png
612 ms
icon_newproducts.png
603 ms
icon_ballistics.png
603 ms
icon_toddlerplay.png
601 ms
icon_interactiveplay.png
603 ms
icon_airtrek.png
603 ms
icon_theming.png
664 ms
icon_installation.png
665 ms
icon_tuffstuff.png
667 ms
image_about.png
1509 ms
image_okada-6.jpg
1025 ms
switcher.png
673 ms
arrow_down.png
754 ms
en.png
754 ms
logo_navi.png
431 ms
Header-Video-Home-3.mp4
3164 ms
image_slider1.jpg
1020 ms
image_slider2_06.jpg
912 ms
icon_mytown.png
533 ms
icon_trampoline.png
535 ms
KFOlCnqEu92Fr1MmWUlfChc-.woff
367 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw3aXw.woff
468 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw3aXw.woff
472 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw3aXw.woff
510 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w3aXw.woff
472 ms
va9c4lja2NVIDdIAAoMR5MfuElaRB0zHt0k.woff
473 ms
va9Z4lja2NVIDdIAAoMR5MfuElaRB0RyklrfPXo.woff
474 ms
proximanova-reg.ttf
690 ms
fontawesome-webfont.woff
747 ms
proximanova-semibold.ttf
813 ms
proximanova-extrabold.ttf
901 ms
va9a4lja2NVIDdIAAoMR5MfuElaRB0zMh0P2Hg.woff
529 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
249 ms
KFOmCnqEu92Fr1Mu4mxM.woff
250 ms
irec.ph accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
Form elements do not have associated labels
Links do not have a discernible name
irec.ph best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
irec.ph SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Irec.ph 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 Irec.ph 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.
irec.ph
Open Graph description is not detected on the main page of IREC. 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: