Tools & Wizards About Us
oksegar.com screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 40

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

oksegar.com

School Uniform KL (Kuala Lumpur), Factory Uniform Supplier Selangor, Uniform Manufacturer Malaysia ~ OK Segar Sdn Bhd

Page Load Speed

12.1 sec in total

First Response

756 ms

Resources Loaded

11.1 sec

Page Rendered

265 ms

oksegar.com screenshot

About Website

Visit oksegar.com now to see the best up-to-date OK Segar content and also check out these interesting facts you probably never knew about oksegar.com

OK Segar Sdn Bhd is a uniform manufacturer company. Our main office is located in Kuala Lumpur (KL), Malaysia.

Visit oksegar.com

Key Findings

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

Performance Metrics

oksegar.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.2 s

1/100

10%

LCP (Largest Contentful Paint)

Value21.4 s

0/100

25%

SI (Speed Index)

Value14.6 s

1/100

10%

TBT (Total Blocking Time)

Value2,490 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.283

43/100

15%

TTI (Time to Interactive)

Value21.1 s

1/100

10%

Network Requests Diagram

oksegar.com

756 ms

www.oksegar.com

1427 ms

font-awesome.css

135 ms

style.css

966 ms

general_v1.css

1212 ms

Our browser made a total of 72 requests to load all elements on the main page. We found that 4% of them (3 requests) were addressed to the original Oksegar.com, 67% (48 requests) were made to Cdn1.npcdn.net and 8% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (5.1 sec) relates to the external source Cdn1.npcdn.net.

Page Optimization Overview & Recommendations

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

Content Size

972.9 kB

After Optimization

905.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Oksegar.com main page is 972.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. 55% of websites need less resources to load. Images take 637.7 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 36.4 kB

  • Original 48.9 kB
  • After minification 47.6 kB
  • After compression 12.5 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 36.4 kB or 74% of the original size.

Image Optimization

-3%

Potential reduce by 19.4 kB

  • Original 637.7 kB
  • After minification 618.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. OK Segar images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 6.9 kB

  • Original 234.5 kB
  • After minification 234.5 kB
  • After compression 227.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

-8%

Potential reduce by 4.3 kB

  • Original 51.8 kB
  • After minification 51.8 kB
  • After compression 47.5 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. Oksegar.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 41 (67%)

Requests Now

61

After Optimization

20

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

oksegar.com

oksegar.com

756 ms

www.oksegar.com

www.oksegar.com

1427 ms

font-awesome.css

font-awesome.css

135 ms

style.css

style.css

966 ms

general_v1.css

general_v1.css

1212 ms

color_style.css

color_style.css

3431 ms

gumby.css

gumby.css

157 ms

sweetalert2.min.css

sweetalert2.min.css

154 ms

style.css

style.css

994 ms

banner.css

banner.css

1951 ms

jquery.min.js

jquery.min.js

65 ms

jquery-migrate-3.0.0.min.js

jquery-migrate-3.0.0.min.js

50 ms

jquery-ui.css

jquery-ui.css

68 ms

jquery-ui.theme.min.css

jquery-ui.theme.min.css

164 ms

jquery.fancybox.js

jquery.fancybox.js

181 ms

jquery.fancybox.css

jquery.fancybox.css

193 ms

slick.css

slick.css

208 ms

slick-theme.css

slick-theme.css

218 ms

slick.min.js

slick.min.js

233 ms

jquery.qrcode-0.12.0.min.js

jquery.qrcode-0.12.0.min.js

244 ms

validate.min.js

validate.min.js

254 ms

janimate.js

janimate.js

264 ms

janimate.css

janimate.css

275 ms

owl.carousel.min.css

owl.carousel.min.css

284 ms

owl.theme.newpages.css

owl.theme.newpages.css

295 ms

owl.carousel.js

owl.carousel.js

308 ms

jquery.colourbrightness.min.js

jquery.colourbrightness.min.js

314 ms

animate.css

animate.css

323 ms

sweetalert2.min.js

sweetalert2.min.js

334 ms

js

js

95 ms

page.js

page.js

68 ms

slicebox.css

slicebox.css

1130 ms

custom.css

custom.css

966 ms

modernizr.js

modernizr.js

1739 ms

jquery.slicebox.js

jquery.slicebox.js

1726 ms

jquery-ui.min.js

jquery-ui.min.js

65 ms

jquery.matchHeight-min.js

jquery.matchHeight-min.js

1137 ms

jquery.dotdotdot.min.js

jquery.dotdotdot.min.js

1149 ms

css

css

33 ms

css

css

50 ms

css

css

56 ms

css

css

58 ms

css

css

18 ms

bg.jpg

bg.jpg

1236 ms

newheader1.jpg

newheader1.jpg

1266 ms

1502076504_11cc6517ac7a46cd35a712f09f38402b_en.jpg

1502076504_11cc6517ac7a46cd35a712f09f38402b_en.jpg

1329 ms

1502157737banner3.jpg

1502157737banner3.jpg

1291 ms

1502076493_en_h-slide.gif

1502076493_en_h-slide.gif

1970 ms

15020912481.png

15020912481.png

1269 ms

15020914642.png

15020914642.png

2280 ms

15020915123.png

15020915123.png

2622 ms

15020915524.png

15020915524.png

3261 ms

15020915735.png

15020915735.png

2308 ms

1502094722p01.png

1502094722p01.png

2656 ms

fbevents.js

fbevents.js

103 ms

sm.25.html

sm.25.html

27 ms

eso.D0Uc7kY6.js

eso.D0Uc7kY6.js

148 ms

xfbml.customerchat.js

xfbml.customerchat.js

146 ms

shadow.png

shadow.png

2697 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

182 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

188 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyWyosBO5Xk.ttf

191 ms

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

ieVo2ZhZI2eCN5jzbjEETS9weq8-_d6T_POl0fRJeyVVpcBO5Xk.ttf

191 ms

1502103194p1.jpg

1502103194p1.jpg

3267 ms

1502102736p4.jpg

1502102736p4.jpg

5082 ms

footer.jpg

footer.jpg

3297 ms

4iCs6KVjbNBYlgoKfw7z.ttf

4iCs6KVjbNBYlgoKfw7z.ttf

117 ms

PbynFmL8HhTPqbjUzux3JEuR9l4.ttf

PbynFmL8HhTPqbjUzux3JEuR9l4.ttf

114 ms

icomoon.ttf

icomoon.ttf

2547 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

2563 ms

np_add_cart.php

np_add_cart.php

886 ms

nav.png

nav.png

4074 ms

Accessibility Review

oksegar.com accessibility score

40

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

oksegar.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

oksegar.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    GB2312

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Oksegar.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Oksegar.com main page’s claimed encoding is gb2312. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

oksegar.com

Open Graph data is detected on the main page of OK Segar. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: