Tools & Wizards About Us
ogaliya.com screenshot

Report Summary

  • 71

    Performance

    Renders faster than
    81% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

ogaliya.com

Ogaliya | Buy or Sell Quality and Authentic Handmade Products from Africa.

Page Load Speed

2.7 sec in total

First Response

220 ms

Resources Loaded

2.5 sec

Page Rendered

61 ms

ogaliya.com screenshot

About Website

Click here to check amazing Ogaliya content. Otherwise, check out these important facts you probably never knew about ogaliya.com

Ogaliya is an aggregator of quality and authentic handmade products in Africa. Products include Jewellery, Bags, Footwear, Clothing, Home Décor, Arts & Crafts.

Visit ogaliya.com

Key Findings

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

Performance Metrics

ogaliya.com performance score

71

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

48/100

10%

LCP (Largest Contentful Paint)

Value3.1 s

76/100

25%

SI (Speed Index)

Value5.8 s

50/100

10%

TBT (Total Blocking Time)

Value360 ms

72/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value6.5 s

59/100

10%

Network Requests Diagram

ogaliya.com

220 ms

ogaliya.com

244 ms

style.min.css

158 ms

theme.min.css

200 ms

header-footer.min.css

215 ms

Our browser made a total of 67 requests to load all elements on the main page. We found that 85% of them (57 requests) were addressed to the original Ogaliya.com, 13% (9 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.3 sec) belongs to the original domain Ogaliya.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 34.0 kB (8%)

Content Size

450.9 kB

After Optimization

416.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 29.9 kB

  • Original 38.2 kB
  • After minification 37.2 kB
  • After compression 8.3 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 29.9 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 3.5 kB
  • After minification 3.5 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. Ogaliya images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.5 kB

  • Original 262.5 kB
  • After minification 262.5 kB
  • After compression 259.1 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

-0%

Potential reduce by 667 B

  • Original 146.6 kB
  • After minification 146.6 kB
  • After compression 146.0 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. Ogaliya.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 52 (95%)

Requests Now

55

After Optimization

3

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ogaliya.com

ogaliya.com

220 ms

ogaliya.com

ogaliya.com

244 ms

style.min.css

style.min.css

158 ms

theme.min.css

theme.min.css

200 ms

header-footer.min.css

header-footer.min.css

215 ms

frontend-lite.min.css

frontend-lite.min.css

280 ms

post-11.css

post-11.css

246 ms

ekiticons.css

ekiticons.css

289 ms

style.css

style.css

313 ms

swiper.min.css

swiper.min.css

356 ms

frontend-lite.min.css

frontend-lite.min.css

378 ms

style.css

style.css

404 ms

post-15.css

post-15.css

443 ms

elegant.css

elegant.css

449 ms

linearicons.css

linearicons.css

475 ms

themify.css

themify.css

511 ms

widget-styles.css

widget-styles.css

652 ms

widget-styles-pro.css

widget-styles-pro.css

680 ms

responsive.css

responsive.css

602 ms

css

css

29 ms

page-transitions.min.js

page-transitions.min.js

619 ms

jquery.min.js

jquery.min.js

712 ms

jquery-migrate.min.js

jquery-migrate.min.js

678 ms

jarallax.js

jarallax.js

761 ms

elementskit-reset-button.css

elementskit-reset-button.css

784 ms

particles.css

particles.css

810 ms

hello-frontend.min.js

hello-frontend.min.js

833 ms

instant-page.min.js

instant-page.min.js

842 ms

frontend-script.js

frontend-script.js

865 ms

widget-scripts.js

widget-scripts.js

1019 ms

anime.js

anime.js

944 ms

parallax-frontend-scripts.js

parallax-frontend-scripts.js

1033 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

989 ms

webpack.runtime.min.js

webpack.runtime.min.js

1006 ms

frontend-modules.min.js

frontend-modules.min.js

1086 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

1102 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

1145 ms

wp-polyfill.min.js

wp-polyfill.min.js

1286 ms

hooks.min.js

hooks.min.js

1182 ms

i18n.min.js

i18n.min.js

1029 ms

frontend.min.js

frontend.min.js

1055 ms

waypoints.min.js

waypoints.min.js

1059 ms

core.min.js

core.min.js

1062 ms

frontend.min.js

frontend.min.js

1119 ms

elements-handlers.min.js

elements-handlers.min.js

1057 ms

animate-circle.min.js

animate-circle.min.js

1097 ms

elementor.js

elementor.js

1076 ms

elementor.js

elementor.js

1078 ms

elementskit-sticky-content.js

elementskit-sticky-content.js

1059 ms

elementskit-reset-button.js

elementskit-reset-button.js

1072 ms

particles.min.js

particles.min.js

1115 ms

ekit-particles.js

ekit-particles.js

1090 ms

parallax-admin-scripts.js

parallax-admin-scripts.js

1077 ms

wrapper.js

wrapper.js

1027 ms

cotton.min.js

cotton.min.js

1000 ms

mouse-cursor-scripts.js

mouse-cursor-scripts.js

997 ms

zo1sRpVqLXvWnVG0e8zGI9MSeRzTCU7erpN5RKaN.jpg

zo1sRpVqLXvWnVG0e8zGI9MSeRzTCU7erpN5RKaN.jpg

960 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrc.woff

15 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrc.woff

18 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrc.woff

22 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrc.woff

25 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrc.woff

31 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrc.woff

30 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrc.woff

30 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrc.woff

31 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrc.woff

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrc.woff

24 ms

elementskit.woff

elementskit.woff

1206 ms

Accessibility Review

ogaliya.com accessibility score

100

Accessibility Issues

Best Practices

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

ogaliya.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 Ogaliya.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 Ogaliya.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

ogaliya.com

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