marriamsayed.com Marriamsayed.com

   
Foodeva Marsay | Recipes · Travel · Reviews · Photography

Domain Summary

What percent of global Internet users visit Marriamsayed.com?

• 5.3E-6% of global Internet users visit Marriamsayed.com

How many people visit Marriamsayed.com each day?

• Marriamsayed.com receives approximately 263 visitors and 413 page impressions per day.

Which countries does Marriamsayed.com receive most of its visitors from?

• Marriamsayed.com is mostly visited by people located in South Africa,United Kingdom,Australia.

How much Marriamsayed.com can earn?

• Marriamsayed.com should earn about $0.86/day from advertising revenue.

What is Marriamsayed.com estimated value?

• Estimated value of Marriamsayed.com is $754.04.

What IP addresses does Marriamsayed.com resolve to?

• Marriamsayed.com resolves to the IP addresses 164.160.91.24.

Where are Marriamsayed.com servers located in?

• Marriamsayed.com has servers located in Johannesburg, Gauteng, 1600, South Africa.

marriamsayed.com Profile

Title:Foodeva Marsay | Recipes · Travel · Reviews · Photography Description:Foodeva Marsay" is my Lifestyle/Food Blog, with which I "Aspire to Inspire" for the pleasure of my Creator above. A simple to understand blog which entails a fusion of my many passions in life.
Edit Site Info

What technologies does marriamsayed.com use?

These are the technologies used at marriamsayed.com. marriamsayed.com has a total of 13 technologies installed in 13 different categories.
Page builders
Elementor Elementor
Advertising
Google AdSense Google AdSense
Analytics
Google Analytics Google Analytics
Miscellaneous
HTTP/3 HTTP/3
Open Graph Open Graph
JavaScript Libraries
jQuery jQuery
jQuery Migrate jQuery Migrate
Web Servers
LiteSpeed LiteSpeed
Caching
Litespeed Cache Litespeed Cache
WordPress plugins
Litespeed Cache Litespeed Cache
Programming Languages
PHP PHP
Performance
Priority Hints Priority Hints
CMS
WordPress WordPress
Blogs
WordPress WordPress
Databases
MySQL MySQL

marriamsayed.com Traffic Analysis

This website is viewed by an estimated 263 visitors daily, generating a total of 413 pageviews. This equates to about 8K monthly visitors. Marriamsayed.com traffic has decreased by 40.64% compared to last month.
Daily Visitors263
48.06%
Monthly Visits8K
40.64%
Pages per Visit1.57
23.77%
Visit duration00:12
76%
Bounce Rate42.55%
65.75%
Is this your site?Verify your site's metrics.
Daily Unique Visitors:
263
Monthly Visits:
7,969
Pages per Visit:
1.57
Daily Pageviews:
413
Avg. visit duration:
00:12
Bounce rate:
42.55%
Global Reach:
5.3E-6%
Monthly Visits (SEMrush):
520
Monthly Unique Visitors (SEMrush):
455
Monthly Visits (SimilarWeb):
7,961
HypeRank:
n/a
SEMrush Rank:
2,394,998
SimilarWeb Rank:
2,745,221
*All traffic values are estimates only.

Traffic sources

Direct:
69.81%
Referral:
0%
Search:
30.19%
Social:
0%
Paid:
0%

Desktop vs Mobile

Desktop:
100.00%
Mobile:
0%

Total Visits Last 3 Months

18.2K
OCT
13.4K
NOV
8K
DEC

Visitors by country

Country
Users%
 
South Africa 59.17%
 
United Kingdom 15.79%
 
Australia 15.56%
 
United States 9.48%

  ▼

SEMrush is a complete on line advertising and marketing platform that gives a extensive variety of gear and functions to help companies and entrepreneurs in enhancing their on line visibility and optimizing their virtual advertising and marketing strategies.
SemRushSemRush
Domain:
  marriamsayed.com
Rank:
(Rank based on keywords, cost and organic traffic)
  2,394,998
Organic Keywords:
(Number of keywords in top 20 Google SERP)
  1,075
Organic Traffic:
(Number of visitors coming from top 20 search results)
  249
Organic Cost:
((How much need to spend if get same number of visitors from Google Adwords)
  $1.00
Full SEMrush Report >>
Last update was 1 hour ago
     
This can take up to 60 seconds. Please wait...

Update will be available in 23 hours
*HypeStat.com is not promoting or affiliated with marriamsayed.com in any way. Only publicly available statistics data are displayed.

Revenue report ▼

Google.com would generate approximately $0.9 per day if the source of income were advertisements, which equates to an estimated monthly revenue of $25.8 and annual gross revenue of approximately $313.9. Based on these figures, the site's net worth is estimated at around $754.

How much would marriamsayed.com make?

Daily Revenue:
$0.86
Monthly Revenue:
$25.80
Yearly Revenue:
$313.90
*All earnings values are estimates only.

Daily earning by country

 
CountryPageviewsEarning
 
Australia 64$0.31
 
South Africa 244$0.19
 
United States 39$0.19
 
United Kingdom 65$0.17

Loss of money due to Adblock?

Daily Revenue Loss:
$0.13
Monthly Revenue Loss:
$3.83
Yearly Revenue Loss:
$46.63
Daily Pageviews Blocked:
35
Monthly Pageviews Blocked:
1,057
Yearly Pageviews Blocked:
12,856

Daily revenue loss by country

 
CountryBlockedLost Money
 
Australia 13$0.06
 
United States 7$0.03
 
United Kingdom 10$0.03
 
South Africa 5$0.00

How much is marriamsayed.com worth?

Website Value:
$754

Ad Experience Report ▼

Summary of the ad experience rating of a website for a specific platform.

Mobile summary

Root domain:
marriamsayed.com
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Desktop summary

Root domain:
marriamsayed.com
Ad filtering:
(Chrome is not filtering ads on your site.)
Off
Status:
(The status of the site that is reviewed for the Better Ads Standards.)
Not reviewed

Abusive Experience Report ▼

Summary of the abusive experience rating of a website.
Root domain:
marriamsayed.com
Enforcement:
(Chrome is not preventing your site from opening new windows or tabs.)
Off
Status:
(The status of the site reviewed for the abusive experiences.)
Not reviewed

Where is marriamsayed.com hosted? ▼

Marriamsayed.com may be hosted in multiple data centers distributed in different locations around the world. This is probably just one of them.
Server IP:
164.160.91.24
ASN:
AS328037 
ISP:
Elitehost 
Server Location:
Johannesburg
Gauteng, GP
1600
South Africa, ZA
 

Other sites hosted on 164.160.91.24

How fast does marriamsayed.com load? ▼

The average loading time of marriamsayed.com is 836 ms. The Desktop speed index is 67 and mobile speed index is 46.
Average Load Time:
836 ms

Page Speed (Google PageSpeed Insights) - Desktop

67
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Cumulative Layout Shift (CLS)2ms 85% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 85% 8% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 8% 5% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 5%
Time To First Byte (TTFB)1.2s 56% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 56% 35% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 35% 7% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 7%
First Contentful Paint (FCP)1.5s 83% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 83% 12% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 12% 4% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 4%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)0 0% of loads for this page have a fast (<0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>0ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.7s 89% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 89% 8% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 8% 2% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 2%

Origin Data

All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Cumulative Layout Shift (CLS)2ms 85% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 85% 8% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 8% 5% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 5%
Time To First Byte (TTFB)1.2s 56% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 56% 35% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 35% 7% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 7%
First Contentful Paint (FCP)1.5s 83% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 83% 12% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 12% 4% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 4%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interaction To Next Paint (INP)0 0% of loads for this page have a fast (<0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have an average (0ms ~ 0ms) Interaction To Next Paint (INP) 0% 0% of loads for this page have a slow (>0ms) Interaction To Next Paint (INP) 0%
Largest Contentful Paint (LCP)1.7s 89% of loads for this page have a fast (<2500ms) Largest Contentful Paint (LCP) 89% 8% of loads for this page have an average (2500ms ~ 4000ms) Largest Contentful Paint (LCP) 8% 2% of loads for this page have a slow (>4000ms) Largest Contentful Paint (LCP) 2%

Lab Data

Total Blocking Time 120 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
First Contentful Paint 0.5 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Time to Interactive 3.3 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Speed Index 2.0 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric
Largest Contentful Paint 3.3 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
Max Potential First Input Delay 100 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
INP breakdown  
Start investigating by looking at the longest subpart. how to improve INP

Page Speed (Google PageSpeed Insights) - Mobile

46
0-49 50-89 90-100 i

Field Data

Over the last 30 days, the field data shows that this page has a AVERAGE speed compared to other pages in the Chrome User Experience Report.We are showing the 90th percentile of FCP and the 95th percentile of FID.

Cumulative Layout Shift (CLS)11ms 85% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 74% 1% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 1% 23% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 23%
Time To First Byte (TTFB)688ms 56% of loads for this page have a fast (<800s) Time To First Byte (TTFB) 77% 16% of loads for this page have an average (800s ~ 1800s) Time To First Byte (TTFB) 16% 5% of loads for this page have a slow (>1800s) Time To First Byte (TTFB) 5%
First Contentful Paint (FCP)1.5s 83% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 82% 11% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 11% 5% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 5%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average (0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)191ms 0% of loads for this page have a fast (<200s) Interactive To Next Paint (INP) 76% 15% of loads for this page have an average (200s ~ 500s) Interactive To Next Paint (INP) 15% 8% of loads for this page have a slow (>500s) Interactive To Next Paint (INP) 8%
Largest Contentful Paint (LCP)1.7s 89% of loads for this page have a fast (<2500s) Largest Contentful Paint (LCP) 86% 9% of loads for this page have an average (2500s ~ 4000s) Largest Contentful Paint (LCP) 9% 3% of loads for this page have a slow (>4000s) Largest Contentful Paint (LCP) 3%

Origin Data

All pages served from this origin have an AVERAGE speed compared to other pages in the Chrome User Experience Report. over the last 30 days.To view suggestions tailored to each page, analyze individual page URLs.

Cumulative Layout Shift (CLS)11ms 74% of loads for this page have a fast (<0.01s) Cumulative Layout Shift (CLS) 74% 1% of loads for this page have an average (0.01s ~ 0.025s) Cumulative Layout Shift (CLS) 1% 23% of loads for this page have a slow (>0.025s) Cumulative Layout Shift (CLS) 23%
Time To First Byte (TTFB)688ms 77% of loads for this page have a fast (<0.8s) Time To First Byte (TTFB) 77% 16% of loads for this page have an average (0.8s ~ 1.8s) Time To First Byte (TTFB) 16% 5% of loads for this page have a slow (>1.8s) Time To First Byte (TTFB) 5%
First Contentful Paint (FCP)1.5s 82% of loads for this page have a fast (<1.8s) First Contentful Paint (FCP) 82% 11% of loads for this page have an average (1.8s ~ 3s) First Contentful Paint (FCP) 11% 5% of loads for this page have a slow (>3s) First Contentful Paint (FCP) 5%
First Input Delay (FID)0 0% of loads for this page have a fast (<0ms) First Input Delay (FID) 0% 0% of loads for this page have an average 0ms ~ 0ms) First Input Delay (FID) 0% 0% of loads for this page have a slow (>0ms) First Input Delay (FID) 0%
Interactive To Next Paint (INP)191ms 76% of loads for this page have a fast (<0.2s) Interactive To Next Paint (INP) 76% 15% of loads for this page have an average (0.2s ~ 0.5s) Interactive To Next Paint (INP) 15% 8% of loads for this page have a slow (>0.5s) Interactive To Next Paint (INP) 8%
Largest Contentful Paint (LCP)1.7s 86% of loads for this page have a fast (<2.5s)Largest Contentful Paint (LCP) 86% 9% of loads for this page have an average (2.5s ~ 4s)Largest Contentful Paint (LCP) 9% 3% of loads for this page have a slow (>4s)Largest Contentful Paint (LCP) 3%

Lab Data

Total Blocking Time 110 ms
Sum of all time periods between FCP and Time to Interactive, when task length exceeded 50ms, expressed in milliseconds. Learn more about the Total Blocking Time metric
Largest Contentful Paint 14.1 s
Largest Contentful Paint marks the time at which the largest text or image is painted. Learn more about the Largest Contentful Paint metric
First Contentful Paint 2.0 s
First Contentful Paint marks the time at which the first text or image is painted. Learn more about the First Contentful Paint metric
Max Potential First Input Delay 90 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric
INP breakdown  
Start investigating by looking at the longest subpart. how to improve INP
Time to Interactive 14.3 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric
Speed Index 6.8 s
Speed Index shows how quickly the contents of a page are visibly populated. Learn more about the Speed Index metric

Does marriamsayed.com use compression? ▼

Website compression is the process of reducing the size of website files, such as HTML, CSS, JavaScript, and image files, to improve website performance and load times. Compressing website files can significantly reduce the amount of data that needs to be transferred from the server to the user's browser, resulting in faster page load times and improved user experience. Files on marriamsayed.com are reduced by 82%.
marriamsayed.com use br compression.
Original size: 239.72 KB
Compressed size: 41.62 KB
File reduced by: 198.1 KB (82%)

Google Safe Browsing ▼

Google Safe Browsing is a service provided by Google that helps protect users from visiting websites that may contain malicious or harmful content, such as malware, phishing attempts, or deceptive software.
This site is not currently listed as suspicious

MyWot.com Reputation Ratings

MyWOT (short for "My Web of Trust") is a web-based reputation and rating service that provides users with information about the trustworthiness and safety of websites.
Status:
  UNKNOWN

SSL Checker - SSL Certificate Verify ▼

An SSL (Secure Sockets Layer) certificate is a digital certificate that establishes a secure encrypted connection between a web server and a user's web browser. It provides authentication and encryption, ensuring that data transmitted between the server and the browser remains private and protected. marriamsayed.com supports HTTPS.
 marriamsayed.com supports HTTPS
     
Verifying SSL Support. Please wait...
Common Name: *.marriamsayed.com
Organization:
Location:
Issuer: R12
Valid from: Jan 15 03:10:12 2026 GMT
Valid until: Apr 15 03:10:11 2026 GMT
Authority: CA:FALSE
Keysize: 2048 Bits
Common Name: R12
Organization: Let's Encrypt
Location: US
Issuer: ISRG Root X1
Valid from: Mar 13 00:00:00 2024 GMT
Valid until: Mar 12 23:59:59 2027 GMT
Authority: CA:TRUE
Keysize: 2048 Bits

Verify HTTP/2 Support ▼

HTTP/2 (Hypertext Transfer Protocol version 2) is a major revision of the HTTP protocol, which is the foundation of data communication on the World Wide Web. It was developed as an improvement over the previous HTTP/1.1 version to enhance web performance and efficiency.
 marriamsayed.com supports HTTP/2
     
Verifying HTTP/2.0 Support. Please wait...

Http Header ▼

HTTP headers are extra portions of records despatched among a consumer (which include an internet browser) and a server at some stage in an HTTP request or response. They offer instructions, metadata, or manipulate parameters for the conversation among the consumer and server. 
x-powered-by: PHP/8.2.29
x-dns-prefetch-control: on
vary: accept, content-type,Accept-Encoding,User-Agent
content-type: text/html; charset=UTF-8
link: <https://marriamsayed.com/wp-json/>; rel="https://api.w.org/"
link: <https://marriamsayed.com/wp-json/wp/v2/pages/216>; rel="alternate"; title="JSON"; type="application/json"
link: <https://marriamsayed.com/>; rel=shortlink
etag: "2562-1769058075;br"
x-litespeed-cache: hit
content-encoding: br
date: Sat, 24 Jan 2026 12:50:02 GMT
server: LiteSpeed
alt-svc: h3=":443"; ma=2592000, h3-29=":443"; ma=2592000, h3-Q050=":443"; ma=2592000, h3-Q046=":443"; ma=2592000, h3-Q043=":443"; ma=2592000, quic=":443"; ma=2592000; v="43,46"

DNS Lookup ▼

DNS entries (Domain Name System) are a critical component of the Internet infrastructure. They act as directories that translate human-readable domain names (such as example.com) to machine-readable IP addresses. DNS records are stored on DNS servers and help forward internet traffic efficiently.
Type Ip Target/Txt TTL
MX marriamsayed.com 14400
A 164.160.91.24 14400
NS ns5.za-dns.com 86400
NS ns3.za-dns.com 86400
SOA 86400
Mname ns3.za-dns.com
Rname servers.za-dns.com
Serial Number 2026011501
Refresh 3600
Retry 7200
Expire 1209600
Minimum TTL 86400