25.5 sec in total
676 ms
24.6 sec
281 ms
Click here to check amazing Obeikan content for Saudi Arabia. Otherwise, check out these important facts you probably never knew about obeikan.com.sa
Visit obeikan.com.saWe analyzed Obeikan.com.sa page load time and found that the first response time was 676 ms and then it took 24.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 3 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
obeikan.com.sa performance score
name
value
score
weighting
Value7.0 s
2/100
10%
Value16.3 s
0/100
25%
Value16.3 s
1/100
10%
Value1,650 ms
12/100
30%
Value0.001
100/100
15%
Value14.9 s
8/100
10%
676 ms
386 ms
549 ms
554 ms
554 ms
Our browser made a total of 111 requests to load all elements on the main page. We found that 95% of them (105 requests) were addressed to the original Obeikan.com.sa, 2% (2 requests) were made to Google-analytics.com and 1% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (20.4 sec) belongs to the original domain Obeikan.com.sa.
Page size can be reduced by 1.4 MB (49%)
2.8 MB
1.4 MB
In fact, the total size of Obeikan.com.sa main page is 2.8 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. 55% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 29.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 29.7 kB or 79% of the original size.
Potential reduce by 110.9 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. Obeikan images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 84% of the original size.
Potential reduce by 167.9 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. Obeikan.com.sa needs all CSS files to be minified and compressed as it can save up to 167.9 kB or 83% of the original size.
Number of requests can be reduced by 86 (82%)
105
19
The browser has sent 105 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Obeikan. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 63 to 1 for JavaScripts and from 18 to 1 for CSS and as a result speed up the page load time.
obeikan.com.sa
676 ms
css.jsp
386 ms
yui.js
549 ms
attribute.js
554 ms
event-custom.js
554 ms
loader.js
555 ms
oop.js
362 ms
aui-base.js
554 ms
modules.js
593 ms
dependency.js
727 ms
language.js
739 ms
liferay.js
722 ms
util.js
737 ms
events.js
723 ms
portal.js
779 ms
portlet.js
967 ms
portlet_sharing.js
958 ms
main.css
967 ms
swfobject_modified.js
962 ms
twoColLiqLtHdr.css
961 ms
shadowbox.css
998 ms
stylesheet.css
1159 ms
jquery.jscrollpane.css
1162 ms
shadowbox.js
1348 ms
jquery.min.js
54 ms
jquery.jscrollpane.min.js
1161 ms
script.js
1188 ms
jquery.mousewheel.js
1335 ms
jquery.cycle.all.js
1337 ms
script_slideshow.js
1338 ms
main.js
1339 ms
base.css
413 ms
application.css
555 ms
layout.css
556 ms
dockbar.css
558 ms
navigation.css
559 ms
portlet.css
563 ms
forms.css
608 ms
extras.css
791 ms
custom.css
2245 ms
custom_common.css
204 ms
green.css
205 ms
orange.css
207 ms
get_flash_player.gif
148 ms
youtube.png
222 ms
twitter.png
222 ms
facebook.png
222 ms
arabic.png
221 ms
logo.jpg
405 ms
1.jpg
2261 ms
2.jpg
4364 ms
3.jpg
2595 ms
4.jpg
4623 ms
5.jpg
4367 ms
6.jpg
4094 ms
7.jpg
7365 ms
IMG_2567.JPG
20445 ms
DSC_0232.JPG
20444 ms
DSC_0043.jpg
20444 ms
service1.png
5904 ms
Plastic.jpg
6107 ms
Liquid-packiging-thumb.jpg
6488 ms
service4.png
8546 ms
cse.js
125 ms
icon.png
7232 ms
header_bg.png
7401 ms
hover-bg.png
7465 ms
square.png
7568 ms
input_shadow.png
7627 ms
submit-bg.png
7735 ms
base-base.js
7778 ms
ga.js
135 ms
cse.js
207 ms
__utm.gif
39 ms
dom-base.js
334 ms
dom-style.js
220 ms
selector-native.js
200 ms
selector-css2.js
409 ms
node-base.js
570 ms
event.js
764 ms
node-style.js
194 ms
dom-screen.js
847 ms
node-screen.js
176 ms
pluginhost.js
798 ms
node-pluginhost.js
166 ms
anim.js
335 ms
collection.js
342 ms
base-pluginhost.js
204 ms
node-event-delegate.js
167 ms
classnamemanager.js
166 ms
widget.js
326 ms
aui-component.js
228 ms
aui-delayed-task.js
183 ms
selector.js
182 ms
aui-selector.js
165 ms
aui-node.js
365 ms
dom.js
434 ms
node.js
1374 ms
plugin.js
201 ms
event-simulate.js
250 ms
node-event-simulate.js
211 ms
node-focusmanager.js
195 ms
selector-css3.js
215 ms
menu.js
197 ms
notice.js
236 ms
queue-promote.js
170 ms
datatype-xml.js
170 ms
io.js
335 ms
json.js
187 ms
poller.js
174 ms
hudcrumbs.js
175 ms
obeikan.com.sa 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
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.
obeikan.com.sa best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Registers an unload listener
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
obeikan.com.sa 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
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 Obeikan.com.sa 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 Obeikan.com.sa 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.
obeikan.com.sa
Open Graph description is not detected on the main page of Obeikan. 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: