7.8 sec in total
1.9 sec
5 sec
896 ms
Visit mobibreak.com now to see the best up-to-date Mobibreak content for Egypt and also check out these interesting facts you probably never knew about mobibreak.com
الموقع #1 في عالم الهواتف والتكنولوجيا في الشرق الأوسط. قسم خاص بالدعم الفني من مراجعات وتقييمات وكيف؟
Visit mobibreak.comWe analyzed Mobibreak.com page load time and found that the first response time was 1.9 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
mobibreak.com performance score
name
value
score
weighting
Value0
0/100
10%
Value0
0/100
25%
Value0
0/100
10%
Value0
0/100
30%
Value0.001
100/100
15%
Value0
0/100
10%
1934 ms
24 ms
17 ms
221 ms
54 ms
Our browser made a total of 119 requests to load all elements on the main page. We found that 61% of them (72 requests) were addressed to the original Mobibreak.com, 7% (8 requests) were made to Tpc.googlesyndication.com and 6% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Mobibreak.com.
Page size can be reduced by 1.4 MB (29%)
5.0 MB
3.5 MB
In fact, the total size of Mobibreak.com main page is 5.0 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. 80% 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. Images take 3.3 MB which makes up the majority of the site volume.
Potential reduce by 224.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 224.1 kB or 82% of the original size.
Potential reduce by 225.8 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. Mobibreak images are well optimized though.
Potential reduce by 514.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 514.1 kB or 59% of the original size.
Potential reduce by 470.1 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. Mobibreak.com needs all CSS files to be minified and compressed as it can save up to 470.1 kB or 84% of the original size.
Number of requests can be reduced by 64 (59%)
108
44
The browser has sent 108 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Mobibreak. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 33 to 1 for JavaScripts and from 8 to 1 for CSS and as a result speed up the page load time.
mobibreak.com
1934 ms
analytics.js
24 ms
gpt.js
17 ms
style.css
221 ms
css
54 ms
styles.css
113 ms
styles-rtl.css
114 ms
rtl.css
328 ms
jetpack-rtl.css
1328 ms
jquery.js
1389 ms
jquery-migrate.min.js
140 ms
ajax.min.js
153 ms
rtl.css
207 ms
library.js
240 ms
adsbygoogle.js
39 ms
pubads_impl_81.js
33 ms
collect
65 ms
bbm_channel_pin.js
324 ms
jquery.form.min.js
222 ms
scripts.js
222 ms
devicepx-jetpack.js
70 ms
core.min.js
220 ms
widget.min.js
222 ms
tabs.min.js
262 ms
mouse.min.js
262 ms
slider.min.js
268 ms
effect.min.js
315 ms
effect-slide.min.js
315 ms
jquery.ui.touch-punch.js
312 ms
hoverIntent.min.js
324 ms
plugins.min.js
455 ms
scripts.min.js
366 ms
addthis_widget.js
50 ms
wp-embed.min.js
366 ms
e-201609.js
49 ms
container.html
32 ms
collect
83 ms
ga-audiences
59 ms
droidarabickufi.css
32 ms
wp-emoji-release.min.js
169 ms
Logo-New.png
93 ms
%D8%B4%D8%A7%D8%B4%D8%A9-%D8%AA%D9%84%D9%81%D8%B2%D9%8A%D9%88%D9%86-Samsung-UE65JS9000.jpg
624 ms
%D8%A8%D9%84%D8%A7%D9%83-%D8%A8%D9%8A%D8%B1%D9%8A-QNX-%D8%AA%D9%85%D9%87%D8%AF-%D8%A7%D9%84%D8%B7%D8%B1%D9%8A%D9%82-%D8%A7%D9%85%D8%A7%D9%85-%D8%A7%D9%84%D9%82%D9%8A%D8%A7%D8%AF%D8%A9-%D8%A7%D9%84%D8%A2%D9%84%D9%8A%D8%A9.jpg
1341 ms
%D8%A7%D9%86%D8%B3%D8%AA%D8%A7%D8%AC%D8%B1%D8%A7%D9%85-%D9%85%D9%88%D8%A8%D9%8A-%D8%A8%D8%B1%D9%8A%D9%83.jpg
189 ms
%D8%B4%D8%A7%D8%AD%D9%86-%D9%85%D8%BA%D9%86%D8%A7%D8%B7%D9%8A%D8%B3%D9%8A-2.jpg
440 ms
654_edit-245x170.jpg
93 ms
1456060126743288-1024x576-245x170.png
433 ms
IMG_20160205_141827.png
1340 ms
1454605152822_927261.jpeg
299 ms
1453331750015_412718.png
614 ms
%D8%A8%D9%84%D8%A7%D9%83-%D8%A8%D9%8A%D8%B1%D9%8A-10.3.2.jpg
815 ms
%D8%AA%D8%B7%D8%A8%D9%8A%D9%82-%D8%B1%D8%B3%D8%A7%D8%A6%D9%84-%D9%81%D9%8A%D8%AF%D9%8A%D9%88-Yahoo-Livetext-.jpg
1309 ms
%D8%AC%D9%88%D8%AC%D9%84-%D8%A8%D9%8A%D9%83%D8%A7%D8%B3%D8%A7-picasa-320x215.jpg
814 ms
blank.gif
812 ms
1456060126743288-1024x576-40x40.png
1306 ms
%D8%A3.jpg
1303 ms
1440230408251_215532.jpeg
1299 ms
1440162036068_051602.jpeg
1326 ms
%D8%AA%D8%AB%D8%A8%D9%8A%D8%AA-%D9%88%D9%8A%D9%86%D8%AF%D9%88%D8%B2-10-2.jpg
1328 ms
DroidKufi-Regular.woff
89 ms
DroidKufi-Bold.woff
211 ms
EYh7Vl4ywhowqULgRdYwIH3uxQAI1Bvm-GxtFNy4yl0.ttf
209 ms
EYh7Vl4ywhowqULgRdYwICxQL91WRy8t8mPvAX_dIgA.ttf
210 ms
ZvcMqxEwPfh2qDWBPxn6ngV_pQ1T3xN3K1c3sB361us.ttf
209 ms
ZvcMqxEwPfh2qDWBPxn6nn06qf9KHRHwsVx7iw5MXmY.ttf
209 ms
ZvcMqxEwPfh2qDWBPxn6nvzeo8SCrGyBsNQUDsw2Qr8.ttf
209 ms
icons.svg
1241 ms
icons.woff
1239 ms
ca-pub-3266037164456806.js
329 ms
zrt_lookup.html
343 ms
show_ads_impl.js
182 ms
%D9%83%D8%A7%D9%85%D9%8A%D8%B1%D8%A7%D8%AA-DSLR-320x215.jpg
1156 ms
%D8%AA%D8%B9%D8%A8%D9%8A%D8%B1%D8%A7%D8%AA-%D9%81%D9%8A%D8%B3%D8%A8%D9%88%D9%83-320x215.jpg
1156 ms
654_edit.jpg
1157 ms
%D8%AA%D8%B9%D8%A8%D9%8A%D8%B1%D8%A7%D8%AA-%D9%81%D9%8A%D8%B3%D8%A8%D9%88%D9%83.jpg
1158 ms
1456060126743288-1024x576.png
1166 ms
%D9%83%D8%A7%D9%85%D9%8A%D8%B1%D8%A7%D8%AA-DSLR.jpg
1161 ms
%D8%AC%D9%88%D8%AC%D9%84-%D8%A8%D9%8A%D9%83%D8%A7%D8%B3%D8%A7-picasa.jpg
1159 ms
ads
200 ms
osd.js
34 ms
ads
862 ms
654_edit-320x215.jpg
878 ms
ads
805 ms
watch-20x20.png
94 ms
galaxy-20x20.png
64 ms
watch-white-20x20.png
64 ms
galaxy-white-20x20.png
65 ms
rev-b-20x20.png
764 ms
app-20x20.png
767 ms
computer-icon-b-1-20x20.png
767 ms
camera-w-20x20.png
768 ms
News-w1-copy-1-20x20.png
768 ms
computer-icon-w-1-20x20.png
767 ms
blackberry-w-copy-20x20.png
769 ms
camera-b-20x20.png
768 ms
news-1-copy-1-20x20.png
769 ms
iphone-w-copy-20x20.png
771 ms
blackberry-b1-copy-40x40.png
770 ms
news-1-copy-1-40x40.png
771 ms
rev-b-40x40.png
772 ms
badge_banner.png
720 ms
C00318031.jpg
718 ms
camera-b-40x40.png
736 ms
m_js_controller.js
691 ms
abg.js
704 ms
computer-icon-b-1-40x40.png
730 ms
loading-2.gif
537 ms
300lo.json
182 ms
googlelogo_color_112x36dp.png
342 ms
10434428659391322667
297 ms
378784852393342141
295 ms
overlay.png
193 ms
light-skin-1.png
192 ms
imgad
282 ms
nessie_icon_tiamat_f_white.png
281 ms
x_button_blue2.png
290 ms
g.gif
206 ms
sh.7c7179124ea24ac6ba46caac.html
147 ms
s
153 ms
mobibreak.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
<frame> or <iframe> elements do not have a title
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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.
mobibreak.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Browser errors were logged to the console
Page has valid source maps
Issues were logged in the Issues panel in Chrome Devtools
mobibreak.com SEO score
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
AR
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Mobibreak.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Arabic language. Our system also found out that Mobibreak.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.
mobibreak.com
Open Graph data is detected on the main page of Mobibreak. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: