Tools & Wizards About Us
odds-n-ends.com screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 94

    Accessibility

    Visual factors better than
    that of 83% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

odds-n-ends.com

coming soon – Internet Mainstreet – Website Services

Page Load Speed

1.3 sec in total

First Response

66 ms

Resources Loaded

1.2 sec

Page Rendered

106 ms

odds-n-ends.com screenshot

About Website

Welcome to odds-n-ends.com homepage info - get ready to check Odds N Ends best content right away, or after learning these important things about odds-n-ends.com

Visit odds-n-ends.com

Key Findings

We analyzed Odds-n-ends.com page load time and found that the first response time was 66 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

odds-n-ends.com performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value5.8 s

15/100

25%

SI (Speed Index)

Value4.5 s

72/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.0 s

64/100

10%

Network Requests Diagram

odds-n-ends.com

66 ms

imainstreet.com

583 ms

style.min.css

57 ms

theme.min.css

89 ms

header-footer.min.css

105 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Odds-n-ends.com, 91% (30 requests) were made to Imainstreet.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (583 ms) relates to the external source Imainstreet.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 877.4 kB (74%)

Content Size

1.2 MB

After Optimization

300.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Odds-n-ends.com main page is 1.2 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. 30% of websites need less resources to load. CSS take 694.0 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 22.2 kB

  • Original 29.3 kB
  • After minification 29.1 kB
  • After compression 7.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 22.2 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 104.4 kB
  • After minification 104.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. Odds N Ends images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 243.0 kB

  • Original 350.2 kB
  • After minification 350.2 kB
  • After compression 107.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 243.0 kB or 69% of the original size.

CSS Optimization

-88%

Potential reduce by 612.2 kB

  • Original 694.0 kB
  • After minification 691.8 kB
  • After compression 81.8 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. Odds-n-ends.com needs all CSS files to be minified and compressed as it can save up to 612.2 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (90%)

Requests Now

30

After Optimization

3

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

odds-n-ends.com

odds-n-ends.com

66 ms

imainstreet.com

imainstreet.com

583 ms

style.min.css

style.min.css

57 ms

theme.min.css

theme.min.css

89 ms

header-footer.min.css

header-footer.min.css

105 ms

frontend.min.css

frontend.min.css

194 ms

post-6.css

post-6.css

107 ms

swiper.min.css

swiper.min.css

136 ms

e-swiper.min.css

e-swiper.min.css

112 ms

frontend.min.css

frontend.min.css

412 ms

all.min.css

all.min.css

220 ms

v4-shims.min.css

v4-shims.min.css

165 ms

global.css

global.css

211 ms

widget-image.min.css

widget-image.min.css

166 ms

widget-heading.min.css

widget-heading.min.css

195 ms

widget-text-editor.min.css

widget-text-editor.min.css

175 ms

post-43.css

post-43.css

204 ms

css

css

48 ms

v4-shims.min.js

v4-shims.min.js

204 ms

hello-frontend.min.js

hello-frontend.min.js

205 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

223 ms

webpack.runtime.min.js

webpack.runtime.min.js

228 ms

jquery.min.js

jquery.min.js

318 ms

jquery-migrate.min.js

jquery-migrate.min.js

236 ms

frontend-modules.min.js

frontend-modules.min.js

321 ms

hooks.min.js

hooks.min.js

257 ms

i18n.min.js

i18n.min.js

258 ms

frontend.min.js

frontend.min.js

292 ms

core.min.js

core.min.js

327 ms

frontend.min.js

frontend.min.js

316 ms

elements-handlers.min.js

elements-handlers.min.js

355 ms

ims_header01.jpg

ims_header01.jpg

63 ms

font

font

29 ms

Accessibility Review

odds-n-ends.com accessibility score

94

Accessibility Issues

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

Links do not have a discernible name

Best Practices

odds-n-ends.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

odds-n-ends.com SEO score

92

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

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

odds-n-ends.com

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