7.9 sec in total
1.8 sec
5.7 sec
382 ms
Welcome to eclipseflags.com homepage info - get ready to check Eclipse Flags best content right away, or after learning these important things about eclipseflags.com
Visit eclipseflags.comWe analyzed Eclipseflags.com page load time and found that the first response time was 1.8 sec and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
eclipseflags.com performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value8.6 s
1/100
25%
Value17.3 s
0/100
10%
Value1,810 ms
9/100
30%
Value0.135
80/100
15%
Value16.9 s
5/100
10%
1838 ms
94 ms
193 ms
262 ms
264 ms
Our browser made a total of 132 requests to load all elements on the main page. We found that 89% of them (117 requests) were addressed to the original Eclipseflags.com, 4% (5 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 (1.8 sec) belongs to the original domain Eclipseflags.com.
Page size can be reduced by 277.2 kB (21%)
1.3 MB
1.0 MB
In fact, the total size of Eclipseflags.com main page is 1.3 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 656.2 kB which makes up the majority of the site volume.
Potential reduce by 197.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. 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 197.0 kB or 84% of the original size.
Potential reduce by 373 B
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. Eclipse Flags images are well optimized though.
Potential reduce by 61.2 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.
Potential reduce by 18.6 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. Eclipseflags.com has all CSS files already compressed.
Number of requests can be reduced by 105 (88%)
119
14
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Eclipse Flags. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 61 to 1 for JavaScripts and from 46 to 1 for CSS and as a result speed up the page load time.
www.eclipseflags.com
1838 ms
style.min.css
94 ms
jquery.selectBox.css
193 ms
font-awesome.css
262 ms
prettyPhoto.css
264 ms
style.css
266 ms
styles.css
267 ms
animate.min.css
268 ms
growl.min.css
279 ms
john-core.min.css
348 ms
gateway.css
350 ms
colorbox.css
351 ms
_new_jquery-ui-1.12.1.css
352 ms
_new_jquery-ui-timepicker-addon.css
353 ms
dashicons.min.css
375 ms
yith-icon.css
436 ms
color-picker.min.css
435 ms
style.min.css
438 ms
elementor-icons.min.css
440 ms
frontend-legacy.min.css
443 ms
frontend.min.css
478 ms
swiper.min.css
521 ms
post-10.css
523 ms
elementor.min.css
524 ms
elementor-grid.min.css
524 ms
all.min.css
529 ms
v4-shims.min.css
568 ms
post-861.css
608 ms
rtwpvs.min.css
610 ms
rtwpvs-tooltip.min.css
610 ms
font-awesome.min.css
612 ms
scrollbar.min.css
618 ms
chosen.min.css
656 ms
slick.min.css
694 ms
default.min.css
695 ms
css
33 ms
style.min.css
698 ms
css
45 ms
w.js
22 ms
js
62 ms
style.min.css
783 ms
style.css
714 ms
megamenu.min.css
556 ms
post-15.css
522 ms
animations.min.css
526 ms
fontawesome.min.css
523 ms
brands.min.css
583 ms
solid.min.css
604 ms
rs6.css
597 ms
wp-polyfill-inert.min.js
528 ms
regenerator-runtime.min.js
532 ms
wp-polyfill.min.js
544 ms
hooks.min.js
570 ms
jquery.min.js
696 ms
jquery-migrate.min.js
588 ms
core.min.js
531 ms
mouse.min.js
531 ms
draggable.min.js
551 ms
slider.min.js
568 ms
jquery.ui.touch-punch.js
620 ms
iris.min.js
577 ms
i18n.min.js
547 ms
color-picker.min.js
556 ms
wpm-public.p1.min.js
578 ms
v4-shims.min.js
611 ms
jquery.selectBox.min.js
665 ms
jquery.prettyPhoto.min.js
630 ms
jquery.yith-wcwl.min.js
591 ms
index.js
589 ms
index.js
589 ms
growl.min.js
622 ms
underscore.min.js
619 ms
wp-util.min.js
582 ms
lazysizes.min.js
542 ms
john-core.min.js
606 ms
rbtools.min.js
704 ms
rs6.min.js
904 ms
jquery.blockUI.min.js
556 ms
add-to-cart.min.js
553 ms
js.cookie.min.js
553 ms
woocommerce.min.js
597 ms
button.js
805 ms
woocompare.min.js
572 ms
jquery.colorbox-min.js
549 ms
datepicker.min.js
774 ms
add-to-cart-variation.min.js
773 ms
front.min.js
769 ms
_new_jquery-ui-timepicker-addon.js
745 ms
g.gif
12 ms
rtwpvs.min.js
728 ms
scrollbar.min.js
689 ms
chosen.min.js
688 ms
slick.min.js
685 ms
tooltip.min.js
664 ms
frontend.min.js
643 ms
megamenu.min.js
649 ms
search.min.js
645 ms
cart-fragments.min.js
645 ms
forms.js
646 ms
webpack.runtime.min.js
637 ms
frontend-modules.min.js
614 ms
waypoints.min.js
544 ms
swiper.min.js
548 ms
share-link.min.js
566 ms
dialog.min.js
567 ms
frontend.min.js
566 ms
87 ms
preloaded-modules.min.js
553 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-B4iFV0Uz.woff
28 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-NYiFV0Uz.woff
48 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-WYiFV0Uz.woff
87 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-2Y-FV0Uz.woff
87 ms
iJWZBXyIfDnIV5PNhY1KTN7Z-Yh-4I-FV0Uz.woff
88 ms
main-icon.ttf
602 ms
dummy.png
602 ms
SDFSD.jpg
696 ms
fontawesome-webfont.woff
706 ms
fontawesome-webfont.woff
676 ms
67 ms
boat-flag.jpg
561 ms
Hand-Sewn-Flags.jpg
586 ms
Flags-With-Poles.jpg
583 ms
Custom-Flags.jpg
578 ms
fa-brands-400.woff
705 ms
fa-regular-400.woff
624 ms
fa-solid-900.woff
731 ms
free.jpg
446 ms
Stock-Designs.jpg
445 ms
advanced_awd4_logo.png
355 ms
74 ms
tuk5trd7hsuof9wamrv71g015y23oy8k.js
239 ms
render.c0490812d97b27f61ea7.js
63 ms
eclipseflags.com accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
eclipseflags.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
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
Page has valid source maps
eclipseflags.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eclipseflags.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 Eclipseflags.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.
eclipseflags.com
Open Graph description is not detected on the main page of Eclipse Flags. 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: